
This is not an immediate solution but I can imagine listing NIX packages as dependencies inside a cabal file, then NIX would create a sandbox with these dependencies and cabal would build in that sandbox. The advantages are that you're not messing around with the underlying operating system's packages, NIX handles all dependencies transitively, and everything is specified declaratively. Sounds like a nice GSoC project :-) You could also do cross GHC version's builds as GHC itself can be sandboxed. Quite intriguing. Michal On Tue, Mar 18, 2014 at 2:16 PM, Michal Antkiewicz < mantkiew@gsd.uwaterloo.ca> wrote:
Certainly NIX is an interesting approach. It already comes with a large base of dependencies, a format for specifying them. NIX can be installed in any Linux distro and serve as an environment for building packages. That might provide a cross-distribution solution to the native dependency problem.
See, a nice post by Oliver Charles
http://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-with-nixos.html
Michal
On Tue, Mar 18, 2014 at 1:59 PM, David Thomas
wrote: Ok, well, if that's the case I'd like to see about remedying that. Anyone have any thoughts as to how to best go about this? I'm not clear on exactly what info lives where, especially across systems. Entirely manual population would be a (barely) acceptable fallback.
On Tue, Mar 18, 2014 at 9:36 AM, Dan Burton
wrote: I have wished for this on multiple occasions. I don't believe such a thing exists as of yet.
-- Dan Burton
On Tue, Mar 18, 2014 at 9:26 AM, David Thomas
wrote: Is there a way to extract this? I'm looking to make it easier for newcomers to my project to get things building across different linux distros.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe