> You do this for keep things in order or because it buys you functionality?
The former. Single shell expression generates many roots:
.nix-gc-roots/dev-shell.drv ->
/nix/store/ivznvsqn40vb6vkccy092ph1ryhlq12w-nixpkgs-patched
.nix-gc-roots/dev-shell.drv-10 ->
On 01/10/16 04:03, Daniel Hlynskyi wrote:
> To complete previous answer.
>
> I create a separate directory .nix-gc-roots, because nix-shell produces
> many roots.
You do this for keep things in order or because it buys you functionality?
> Also, I haven't found yet a way to get nix root for
To complete previous answer.
I create a separate directory .nix-gc-roots, because nix-shell produces
many roots. Also, I haven't found yet a way to get nix root for nixpkgs
imported as external derivation, so after garbage collect I still have to
redownload some sources
30 вер. 2016 4:44 пп
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Sep 30, 2016 at 10:30:27AM -0300, Ruben Astudillo wrote:
> hi
>
> nix-shell is great, but when I update the nixpkgs or nix-collect-garbage
> I lose the cache of those packages. I've thinking on do a special profile
> that I could switch to
hi
nix-shell is great, but when I update the nixpkgs or nix-collect-garbage
I lose the cache of those packages. I've thinking on do a special profile
that I could switch to per shell instance with nix-{shell,env}, but I
also found references to a deprecated buildEnv function for this. What is
