Re: [Nix-dev] Tracking down dependencies

2015-01-29 Thread Thomas Bereknyei
Thanks everyone, it's exactly what I was looking for. On Thu, Jan 29, 2015 at 4:56 AM, Georges Dubus wrote: > The nox-update command (in the nox package) is an attempt to provide such > information. It present the dependency tree of the derivation that are > about to be installed by nixos-rebuil

Re: [Nix-dev] Tracking down dependencies

2015-01-29 Thread Georges Dubus
The nox-update command (in the nox package) is an attempt to provide such information. It present the dependency tree of the derivation that are about to be installed by nixos-rebuild switch. You can see an example there : https://github.com/madjar/nox#experimental Georges Dubus 2015-01-29 10:49

Re: [Nix-dev] Tracking down dependencies

2015-01-29 Thread Andreas Herrmann
On Wednesday 28 January 2015 13:23:08 Thomas Bereknyei wrote: > During a recent `nixos-rebuild switch --upgrade` I noticed gtk+ being > downloaded from cache. Is there a quick way to discover what is causing > that to be needed? [Rather than going through all of my configuration.nix > packages one-

Re: [Nix-dev] Tracking down dependencies

2015-01-28 Thread Rok Garbas
Quoting Thomas Bereknyei (2015-01-28 19:23:08) > During a recent `nixos-rebuild switch --upgrade` I noticed gtk+ being > downloaded from cache. Is there a quick way to discover what is causing that > to > be needed? [Rather than going through all of my configuration.nix packages > one-by-one?] Thi

[Nix-dev] Tracking down dependencies

2015-01-28 Thread Thomas Bereknyei
During a recent `nixos-rebuild switch --upgrade` I noticed gtk+ being downloaded from cache. Is there a quick way to discover what is causing that to be needed? [Rather than going through all of my configuration.nix packages one-by-one?] This question is also generic, is there a way to do this in g