On Wed, Oct 15, 2014 at 9:07 AM, Sven Panne
And for other packages I even have to add several --constraint flags, because they depend on several locally modified packages. This seems a bit weird. Is this the recommended workflow? How do other maintainers of platform packages handle this? What one *actually* wants is hiding some of the globally exposed packages while being in the sandbox (--constraint and --force-reinstalls could go away then), but I've found no way to do that.
As I understand it, ghc doesn't give cabal enough hooks into its package management to do it properly. I'd be looking at hsenv to set up a sandboxed ghc instead. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net