Mathieu Boespflug

@gregestren thinking about this more, perhaps a generic `package_manager` constraint setting is misguided: package managers are not necessarily mutually exclusive. Perhaps it makes more sense to have multiple "feature test"...

@andreabedini gotten somewhere?

@andreabedini I saw you opened #381, which creates a whole new `cabal`-based CI workflow. The issue reported here can be reproduced with either Stack or cabal-install. It's just that #366...

See https://github.com/tweag/HaskellR/issues/257. In more detail, what's happening here is that on Fedora, packages on hardened by default. Binaries are built as PIE's. But it's not GCC doing that behind people's...

#379 has a proposed fix, along the lines explored by @angerman above: removal of the GC-related functions, removal of `pokeHExp`, etc. Turns out that the getter functions are enough, because...

We could solve that by maintaining maps from GHC (version, platform) -> partial file list. Even host that on a server somewhere if not in rules_haskell itself. After all, we're...

> Hosting them separately is an interesting idea. That would avoid bloating the repo too much. We could amend the bindist mapping with URLs and hashes of these hosted metadata...

Interesting numbers. Ideally we wouldn't need to list all files. Just know where they are given the version number and the platform. Perhaps this could be achieved with `ctx.actions.declare_directory()`. The...

I asked the question on ghc-dev@: https://mail.haskell.org/pipermail/ghc-devs/2020-August/019126.html. The thread seems to indicate that having upstream ship relocatable bindists with a much simpler configure step that only writes out the `settings`...

It's also possible to set this at the level of the toolchain (see the [toolchain rules](https://release.api.haskell.build/haskell/ghc_bindist.html#haskell_register_ghc_bindists)). But then it will apply for all Haskell targets. Not sure whether that's what...