You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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: