Open bgohla opened 1 month ago
I don't see a reason why this should be the case.
The freeze file specifies an exact build plan that must not be altered, but you want to alter it via the flags (which could use different dependency versions or remove/add dependencies), then what is the point of having a cabal freeze file?
I think (although I don't think it should be done) I would at least require a flag like --override-freeze-file to be passed so that you declare "I know for sure that I will break my freeze file declaration and I'm ok with it", but I think what you propose should not by any means be the default.
I mean i guess it would be acceptable to pass an extra flag. But isn't it commonly understood that command line flags override configuration in files?
I want to be able to do this, because I have a code base, which I need to be able to compile with different flag settings.
Describe the feature request A simple description of what you would like to be added to Cabal.
Given a project as follows:
running
should build the
cabal-freeze-bug
package with the flag turned off, instead of failing with a resolution conflict.(Likewise for
cabal build -c"cabal-freeze-bug -some-flag"
)Additional context Related to https://github.com/haskell/cabal/issues/10439