[Haskell-cafe] Listing native package requirements based on cabal information

[Michal Antkiewicz]

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 <davidleothomas at gmail.com>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 <danburton.email at gmail.com>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 <davidleothomas at gmail.com>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 at haskell.org
>>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>>
>>>
>>
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
>

<mantkiew at gsd.uwaterloo.ca>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20140318/a8bdf8a7/attachment.html>