Hello Felix, Felix Yan <felixonmars@archlinux.org> writes:
On 06/26/2017 09:42 PM, Sebastian Reuße via arch-general wrote:
Can you advise whether it’s currently possible to do sandboxed static builds at all? The issue I’m running into is that Cabal won’t install sandboxed dependencies if it sees that the corresponding packages are already registered within the global package DB; the build will proceed but will then error out during static linking.
With the current package set the only way I have in mind is to install stack and start from there. This is unfortunately the same for C libraries since our removal of their static libs.
An idea is to provide an alternative package database in the ghc-static package that only contains the boot libraries. You will need to ignore global package database and specify that alternative path to use it. Does this sound like useful?
That does sound preferable to not being able to do sandboxed static builds at all. I’ll also try pinging the Cabal folks when I get a chance; maybe it would make sense for cabal-install to be able to enforce reinstallation of dependencies without listing all packages explicitly. Kind regards, SR -- Insane cobra split the wood Trader of the lowland breed Call a jittney, drive away In the slipstream we will stay