Eelco Dolstra <[EMAIL PROTECTED]> writes: > Try "nix-env -q --tree" (or --graph in conjunction with dot). It will show > where all those dependencies are coming from. Though if you want to know > which > particular file causes a dependency you'll have to use grep :-)
Thanks for the hints! This is fixed as of r12714: a stupid substitution captured the value of $PATH in a script that gets installed... Ludo'. _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
