Hi Vladimir,
I understand now why my issue is.
I used a path to a symbolic link, which points to my source folder. Nix do handle symbolic links to folders different to real folders. Now I understand more wired problems I had with symbolic links. In a single-user Nix store, Nix used this path as build environment. All pathes and fixed have been applied in my source folder.
I will forward this issue to Nix.
Thanks for the fast help.
Best regards
Christian
Gesendet: Samstag, 11. Februar 2017 um 10:53 Uhr
Von: "Vladimír Čunát" <vcu...@gmail.com>
An: "Christian Kögler" <c...@gmx.de>
Cc: nix-...@science.uu.nl
Betreff: Re: [Nix-dev] multi-user Nix store access problem
Von: "Vladimír Čunát" <vcu...@gmail.com>
An: "Christian Kögler" <c...@gmx.de>
Cc: nix-...@science.uu.nl
Betreff: Re: [Nix-dev] multi-user Nix store access problem
Hello, your'e welcome!
On 02/11/2017 10:35 AM, "Christian Kögler" wrote:
> I do not want to grant nix-daemon access rights to my private folder,
> otherwise other users on that machine have access to my data.
Note that after fetching into nix store the data becomes world-readable.
For my development I combine the following two approaches.
For less frequent builds I use `src = "" # or some other path`. That
causes nix to copy the whole directory to the nix store and pass that
path into the variable. You can use such values as inputs to `fetchgit`
and similar, but the approach has multiple disadvantages.
For standard development cycle - edit, compile, run tests - I use
nix-shell --pure to set up an environment in the current git checkout
and compile by `make` invocation directly in the checkout.
--Vladimir
On 02/11/2017 10:35 AM, "Christian Kögler" wrote:
> I do not want to grant nix-daemon access rights to my private folder,
> otherwise other users on that machine have access to my data.
Note that after fetching into nix store the data becomes world-readable.
For my development I combine the following two approaches.
For less frequent builds I use `src = "" # or some other path`. That
causes nix to copy the whole directory to the nix store and pass that
path into the variable. You can use such values as inputs to `fetchgit`
and similar, but the approach has multiple disadvantages.
For standard development cycle - edit, compile, run tests - I use
nix-shell --pure to set up an environment in the current git checkout
and compile by `make` invocation directly in the checkout.
--Vladimir
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
