On 06/13/2014 07:13 AM, Wout Mertens wrote:
> When you compile things, they will store the absolute paths to their
> dependencies, be it libraries, fonts, datafiles...
> 
> If it didn't do that, installs wouldn't be stateless.
> 
> Try asking your sysadmin if you can have /nix, you never know :-)

I plan to but I'm doubt they'll agree.

> In any case, if you don't manage to compile Nix, perhaps you can use the
> binary install with lots of LD_LIBRARY_PATH-ing.

Oh, I managed to install it and get it running, just looking to reduce
installation time and space requirements. I only have 2GB to work with
overall, including losing few hundred just to get nix and its
dependencies going.

> Wout.
> 
> PS: /nix is hard-coded in a couple of places, too. Those need fixing.
> On Jun 13, 2014 6:22 AM, "Mateusz Kowalczyk" <[email protected]>
> wrote:
> 
>> In the Nix manual it says:
>>
>> ##
>>
>> It is best not to change the Nix store from its default, since doing so
>> makes it impossible to use pre-built binaries from the standard Nixpkgs
>> channels — that is, all packages will need to be built from source.
>>
>> ##
>>
>> I'd like to know why it is impossible. I don't understand why it matters
>> in the slightest whether the store sits at /nix/store or
>> somewhereelse/nix/store. Why does it even know the difference? Are there
>> plans to improve on this? After all, everything would still be in the
>> same relative location to the store. I'm not even sure if it actually
>> means that it is in fact impossible with how nix is designed as opposed
>> to ‘it's not currently implemented’.
>>
>> In environments where one only has regular user rights resources are
>> often constrained, be it hard drive space, memory or computational
>> power. Incurring the penalty of having to compile everything on top of
>> that merely because the store is not sitting at the top of the file
>> system is rather sub-optimal so it would be great if there was a solution.
>>
>> --
>> Mateusz K.
>> _______________________________________________
>> nix-dev mailing list
>> [email protected]
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
> 


-- 
Mateusz K.
_______________________________________________
nix-dev mailing list
[email protected]
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Reply via email to