-
Notifications
You must be signed in to change notification settings - Fork 698
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
Comments
4 tasks
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.
4 tasks
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.
This was referenced Oct 17, 2023
Closing in favour of #8283 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Here's some ideas for how to improve
cabal outdated
with the nix-local-build UI in mind:cabal outdated
should support target-selectors likenew-build
et al:cabal outdated all
would then iterate over all local packages configured incabal.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 yourcabal.project
.cabal outdated
already supportscabal.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 combinescabal new-freeze
withcabal outdated --new-freeze-file
but without generating/overwriting an existingcabal.project.freeze
file./cc @phadej @23Skidoo
The text was updated successfully, but these errors were encountered: