-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's in a name? #114
Comments
That's the syntax of a valid identifier. My point was that the comment in the nix pill doesn't make clear (I think) the purpose of the 'name' attribute in a derivation, which is a slightly different thing I belive. |
I find it slightly confusing with the |
the maybe this will help:
|
for most packages, the name of a package gets determined here: https://github.com/NixOS/nixpkgs/blob/6b2504f9f20e79711e835ef412173ee2be542dc2/pkgs/stdenv/generic/make-derivation.nix#L191 and the store-path (hash + name) isn't determined until it needs to generate a .drv or dervation file (as it will need to evaluate all of the dependencies before this is deterimined) |
Thanks - but my point is not that I don't understand it (I think I do) but that the pill could be reworded slightly to make it easier to grok :) |
problem is that name can be used to describe a store-path-name, a derivation-name, and a package-name ;( |
I found this line confusing in pill 6:
It's a little hard to scan. Also I think there's a distinction between a human readable name ("coreutils") and the name of a derivation (with a hash). So how about something like:
The text was updated successfully, but these errors were encountered: