Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve outdated support for nix-local-build #4831

Closed
hvr opened this issue Oct 19, 2017 · 1 comment
Closed

Improve outdated support for nix-local-build #4831

hvr opened this issue Oct 19, 2017 · 1 comment

Comments

@hvr
Copy link
Member

hvr commented Oct 19, 2017

Here's some ideas for how to improve cabal outdated with the nix-local-build UI in mind:

  • cabal outdated should support target-selectors like new-build et al:

    cabal outdated all would then iterate over all local packages configured in cabal.project and check all components for over-constricted bounds.

    And it also makes sense to limit outdated to some components, i.e. if only care about a few components (and e.g. not the testsuite): cabal outdated lib:foo exe:doo would only check the two named components in whichever local package they're located.

    Conversely, we have special names to e.g. refer to all testsuites in the target-selector; so you could also say cabal outdated tests to iterate over all test-suite components in your cabal.project.

  • cabal outdated already supports cabal.project.freeze; however, it would be convenient to have a variant which consults the last computed install-plan (and possibly compute one if it's needs (re)computation); IOW, a variant that combines cabal new-freeze with cabal outdated --new-freeze-file but without generating/overwriting an existing cabal.project.freeze file.

/cc @phadej @23Skidoo

@23Skidoo 23Skidoo self-assigned this Nov 3, 2017
quasicomputational added a commit to quasicomputational/cabal that referenced this issue Jul 30, 2018
This doesn't get anywhere near the improvements suggested in haskell#4831,
but it's a very respectable improvement over the status-quo for not
much effort.
quasicomputational added a commit to quasicomputational/cabal that referenced this issue Jul 30, 2018
This doesn't get anywhere near the improvements suggested in haskell#4831,
but it's a very respectable improvement over the status-quo for not
much effort.
23Skidoo pushed a commit that referenced this issue Jul 31, 2018
This doesn't get anywhere near the improvements suggested in #4831,
but it's a very respectable improvement over the status-quo for not
much effort.
@andreabedini
Copy link
Collaborator

Closing in favour of #8283

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants