brandon s allbery kf8nh

Another place I'd consider a cabal hook is SCM support (cf. #9883) — ideally we'd just drop a script somewhere rather than needing to add it into cabal-install and make...

Because users will find a way to abuse anything you give them? </sysadmin>

I find myself wondering how that would interact with other things that wrap ghc (such as HLS) as well.

What's happening there is that standard `tar` recognizes tarball names with a colon in them and treats them as _hostname_`:`_filename_, handing them off to `rmt`. That's what `--force-local` was disabling.

As pointed out on today's call, we might instead move the slower checks and tests on older ghc versions to a daily run on `master`.

This is the wrong thing to do if `Main` exports other functions, and assuming every Haskell programmer uses HLS is not appropriate.

I don't seem to be able to reproduce this locally with a just-built `HEAD`. ``` hilfy «cabal:master» Z$ cp $(cabal list-bin cabal) ~/.local/bin/cabal-head Warning: this is a debug build of...

Still happens with 3.10.3.0.

> You are right that HEAD appears to work.. but you shouldn't require HEAD cabal-install to develop cabal-install! No, but > Can the patch responsible please be reverted quickly? implies...

It's _already reverted_. What do you want, that we retroactively re-release 3.10.2 without whatever it was?