I never use the Haskell Platform with nix, because nixpkgs.haskellPackages
is already a curated package set that always seems to work together.
Perhaps people transitioning projects to nix from other platforms would get
some benefit out of having access to the Platform as such, but in my
context (several moderately large commercial projects), it doesn't come up.

On Fri, Nov 7, 2014 at 2:11 PM, Peter Simons <sim...@cryp.to> wrote:

> Hi guys,
> Haskell Platform 2014.2.0.0 has been released a while ago, and I can't
> help noticing that no-one seems to be in a hurry to add that to Nixpkgs.
> Apparently, there not much of a demand for Haskell Platform in Nix?
> This makes me wonder about the old HP releases that we still have:
> 2009.2.0.2, 2010.1.0.0, 2010.2.0.0, 2011.2.0.0, 2011.2.0.1, 2011.4.0.0,
> 2012.2.0.0, 2012.4.0.0, and 2013.2.0.0.
> All of those builds were pretty much non-functional until recently
> because none of them actually installed a compiler into the user
> profile, but no-one noticed that for a period of several months.
> Having those old versions around forces us to keep ancient versions of
> many HP member packages like HTTP, mtl, vector, etc., too, and that adds
> a bit of complexity to Nixpkgs. Since no-one seems to *use* that stuff,
> I'm tempted to say that we should drop support for Haskell Platform
> altogether and to throw out all these ancient package versions in the
> process.
> How do others feel about that? Do you desperately want to be able to
> install Haskell Platform 2010.2.0.0 any time soon?
> Best regards,
> Peter
> _______________________________________________
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
nix-dev mailing list

Reply via email to