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
When testing an unreleased version of GHC with a haskell project, usually the haskell dependencies have upper bounds that prevent the newer bootstrap libraries from being used.
With stack and cabal one can use a flag allow-newer to try building the packages even when their bounds ask for older libraries.
In the current state of rules_haskell, one has to patch all the packages in the dependency tree that need bounds relaxed.
A more convenient solution would be to add an attribute "allow_newer" to stack_snapshot that directs both stack and cabal to switch on their respective allow-newer flags.
The text was updated successfully, but these errors were encountered:
Turns out that --allow-newer is supported by cabal-install, but not by Setup.hs/Cabal haskell/cabal#3581
Apparently Setup.hs can be told to ignore the bounds, but then one has to be more explicit about deps and flag settings on the command line. It wouldn't be as simple as passing a flag.
When testing an unreleased version of GHC with a haskell project, usually the haskell dependencies have upper bounds that prevent the newer bootstrap libraries from being used.
With stack and cabal one can use a flag
allow-newer
to try building the packages even when their bounds ask for older libraries.In the current state of rules_haskell, one has to patch all the packages in the dependency tree that need bounds relaxed.
A more convenient solution would be to add an attribute "allow_newer" to
stack_snapshot
that directs both stack and cabal to switch on their respectiveallow-newer
flags.The text was updated successfully, but these errors were encountered: