Hi Michael,
>> why don't you just add those tools into your user's profile?
>
> The short answer is that the examples I gave weren't the best, they
> were just what sorted first in my list of Haskell development
> tools---the ones I believe must be instantiated in that environment
> in order
Hi, Peter,
On Fri, Mar 6, 2015, at 07:42 AM, Peter Simons wrote:
> why don't you just add those tools into your user's profile?
That's a reasonable question, with two answers:
The short answer is that the examples I gave weren't the best, they were
just what sorted first in my list of Haskell de
Many thanks, Daniel, that's exactly the sort of thing I was looking for.
Mike.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Yes, Rich, that's very helpful.
Mike.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Everyone seems to have their own way of doing it. Recently I've been using
a script to create the environment I like [1]. The only prereq is that a
default.nix exists. Then it checks for a shell.nix, and if present, uses
that. This gives me the ability to override existing packages. Otherwise
it
Hi Michael,
> I would like to be able to maintain both a default.nix (that
> represents the library dependencies, etc.), and then have a shell.nix
> that adds things to it in order to build a development
> environment---specifically some build tools, hasktags, hlint, etc.
why don't you just a
On 2015-03-06 at 13:24, Michael Alan Dorman wrote:
> In developing a haskell library, I would like to be able to maintain
> both a default.nix (that represents the library dependencies, etc.), and
> then have a shell.nix that adds things to it in order to build a
> development environment---specif
In developing a haskell library, I would like to be able to maintain
both a default.nix (that represents the library dependencies, etc.), and
then have a shell.nix that adds things to it in order to build a
development environment---specifically some build tools, hasktags,
hlint, etc.
http://www.c
