Hi there,
I’m pretty new to NixOS, and I’m trying to get into using it for Haskell
development. So far, I’ve been following the guide here
(http://wiki.ocharles.org.uk/Nix) with moderate success for libraries that
don’t directly need to interact with C/C++ libraries. However, I’ve got some
pro
(Don't forget to copy the list.)
On 7 March 2015 at 00:17, CodeHero wrote:
> Now I used the full path to ld-linux-x86-64.so.2 and the file-not-found
> error does not occur. However now there's another problem
> "/nix/store/HASH-firefox-nightly/bin/.firefox-nightly-wrapped: error while
> loading s
On 6 March 2015 at 23:59, Bjørn Forsman wrote:
> On 6 March 2015 at 23:33, CodeHero wrote:
>> Okay. I tried patching the firefox-bin with "patchelf --set-interpreter
>> ${glibc}/lib/ld-linux.so firefox-bin" before using nix-build, but the "does
>> not exist" message still appears.
>>
>> Using "${
On 6 March 2015 at 23:33, CodeHero wrote:
> Okay. I tried patching the firefox-bin with "patchelf --set-interpreter
> ${glibc}/lib/ld-linux.so firefox-bin" before using nix-build, but the "does
> not exist" message still appears.
>
> Using "${glibc}/lib/ld-linux.so ..." just results in "bash:
> /l
On 6 March 2015 at 23:00, CodeHero wrote:
> So I tried to run firefox nightly by downloading the tar from
> https://nightly.mozilla.org/ and installing a wrapper with the
> directions from
> https://nixos.org/wiki/FAQ#I.27ve_downloaded_a_binary.2C_but_I_can.27t_run_it.2C_what_can_I_do.3F.
> Howeve
So I tried to run firefox nightly by downloading the tar from
https://nightly.mozilla.org/ and installing a wrapper with the
directions from
https://nixos.org/wiki/FAQ#I.27ve_downloaded_a_binary.2C_but_I_can.27t_run_it.2C_what_can_I_do.3F.
However that did not work. When I try to run the wrapp
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
Hi again.
TL;DR: on a slow HDD the slow-down can be noticeable, especially for
large packages with lots of files.
On 02/12/2015 11:47 AM, Wout Mertens wrote:
Disadvantages:
- Need to checksum all files written to the store
* this is fast while writing the files because they still are in ca
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
11 matches
Mail list logo
