[Nix-dev] haskell structure for all of nixpkgs

[Eric Merritt]

Stewert,

I did the majority of the Erlang/Beam packaging and I followed the Haskell model for two main reasons.

1. It worked so well in Haskell - why deviate?
2. Expression generation was much easier.


I think these strongly win out, at at least for the Erlang/Beam world. The downside is that grepping the
nixpkgs repository (my default way to search for a package) doesn't work nearly as well.

My suspicion is that, if you wanted to go this route generally, you would need to improve the tooling
around searching for packages/expressions.

Eric



-------- Original Message --------
Subject: Re: [Nix-dev] haskell structure for all of nixpkgs
Local Time: April 25, 2016 10:26 AM
UTC Time: April 25, 2016 5:26 PM
From: setori88 at gmail.com
To: domen at dev.si
CC: nix-dev at lists.science.uu.nl

Okay Domen's a +1, maybe the guys and girls who implemented haskell
like PL level package systems could weigh in with insight. For example
ICIUC, Erlang packages adopts the same approach. The gained knowledge
could be helpful to start with this document.

Could someone with experience please write, in this thread, a few
words about this approach? Keep it small and simple.

Hopefully this gets more people interested by understanding it. Domen
says it's advanced and simple... why is it advanced and simple?
_______________________________________________
nix-dev mailing list
nix-dev at lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160425/aba70a0a/attachment.html