Matthew Pickering

@Mikolaj I don't have any particular more comments to what I already made (there is no a priori reason that using a new Cabal library version will continue to work...

I require the version to be bumped to 3.13 before this can be finished.

The test fails on 8.6.5 because of this GHC bug (fixed in 2018): e400b9babdcf11669f963aeec20078fe7ccfca0d

Can someone please review this patch? I would like to get it off my plate as I have been working on it for quite a while.

I made two recent improvements. * Better handling of -dynamic-too * Enforce that Cabal >3.13 constraint applies to all setups if profiling dynamic is used anywhere (this is conservative).

> I feel the code to handle "way" keeps getting more and more complex. Is there any way we can reduce this complexity? > > E.g. do we really need...

I am using ``` cabal --version cabal-install version 3.10.2.1 compiled using version 3.10.2.1 of the Cabal library ``` You are right that HEAD appears to work.. but you shouldn't require...

@geekosaur Normal development practice is regressed because the current state of the repo doesn't work with existing developer workflows with a released version of cabal-install. (Arguably an even more critical...

I expect that developers provision `cabal-install` from their system package manager therefore the code base should work with at least the most recent released version of `cabal-install`. When this error...

Seems related to #9669 The preferred versions file from hackage is here: https://hackage.haskell.org/packages/preferred-versions It seems that the solver looks at preferences first (and no way to control this at the...