brandon s allbery kf8nh

Have you tried it with the cabal-head prereleases? Those should soon be prepared for release now that we have an alpha 9.12. (Which reminds me I need to file a...

Yes, but this is about checking whether the prerelease to hopefully be made available there soon will work.

FWIW I mentioned the benchmarks case; the original proposal was somewhere else (possibly Matrix?), and benchmarks were mentioned there as a possibility.

I will also concur with not liking the idea of these being accessed from mainline (i.e. not tests or benchmarks) code: that pretty much shreds SemVer/PVP/etc.

Tests and benchmarks changing build plans is _already_ an issue; that's the primary reason that you need to use `build` with `--enable-tests` or `--enable-benchmarks`.

That's just a lousy error message: `--enable-tests` is the same as `tests: True` in the project file, as @Bodigrim said (in the part you quoted, even!), and without enabling the...

I have no idea; I don't know Windows that well.

`Setup.hs` is the CLI interface to the Cabal library. Back before cabal-install and stack existed, the usual way to install a package was ``` $ runghc Setup.hs configure [parameters] $...

The solver is part of `cabal-install`, not `Cabal`. It's inextricably linked to the store and to `pkg-config` among other things, none of which `Cabal` and therefore `Setup` know about.

I'm going to wait a few days for one of the other maintainers to look at it, but as they're often unavailable I won't wait too long.