brandon s allbery kf8nh

``` commit 8ff3134ed4aa323b0199ad683f72165e51a59ab6 Author: Matthew Pickering Date: Tue Sep 15 07:42:18 2020 +0100 Revert "Pass preprocessor options to C compiler when building foreign C files (#16737)" This reverts commit 1c18d3b41f897f34a93669edaebe6069f319f9e2....

``` Integration tests (internal) Target selectors problems (common): FAIL Exception: Error: [Cabal-7107] Could not resolve dependencies: [__0] trying: q-0.1 (user goal) [__1] next goal: filepath (dependency of q) [__1] rejecting:...

But… shouldn't the `filepath` installed with the GHC 9.10 prerelease _already_ allow the `base` shipped along with it? (Although I did wonder if that was why the peculiar rejection message.)

Arguably that calls for 3.10.3.1 to reexport it, since API changes like that seem wrong.

The reason it's part of the solver is that existence of pkg-config packages can be used to conditionalize build plans, e.g. falling back to a slower pure-Haskell package if a...

I'd even consider having `cabal update` update both caches, rather than having users deal with two separate commands. Ultimately the real problem here is `pkg-config` itself, but I don't think...

Seems like the correct course of action is to capture the sdists from a build as artifacts and generate a local no-index repo from them, then do a build without...

#6955 claims that releases are done from sdists, but in fact they're done from a clone of this repo on Gitlab. I think that's necessary, since they need to be...

@ulysses4ever didn't understand the problem from the above description, so I'll try to expand upon it. `cabal-install-3.10.3.0` initially had `Cabal ^>= 3.10` in its `build-depends` (https://hackage.haskell.org/package/cabal-install-3.10.3.0/revision/0.cabal). If the ghc used...

FTR, it's been decided that that change should not have been backported, so I am revising my WIP (not yet a PR) to fail if it happens again.