Jonathan Ringer

actually, this might be a bit more involved, as I believe people need to have `nix command` experimental feature

another option would be to install in both locations, to avoid breaking changes for individuals

Also, added the headers as part of the install target, so that `cmake --build --target install` should be all that downstream users need to do for installation.

Bump, as this came up again: https://discourse.nixos.org/t/21-05-retrospective/13426/8 Specifically for ZHF, it would be nice for people who have listed themselves as maintainers to see a concise view of builds that...

I think one issue is that there's not one problem that nix + nixos is trying to solve. nix-pills is more oriented around understanding so that you can apply it...

this does a little more than update the `:b` command, are you sure that you included the right changes?

I second this motion, I would love for there to be something to ease you into nixos modules. @Infinisil since he has the most knowledge on the subject (besides eelco,...

the `name` of a derivation is usually: `{pname}-{version}`, however a store path is usually the `{hash}-{pname}-{version}`. maybe this will help: ``` [09:24:15] jon@jon-desktop /home/jon/projects/nixpkgs (master) $ nix eval nixpkgs.python3.outPath "/nix/store/gpnm7i19lpj8p43mjrdw03d0hjalmskl-python3-3.7.5"...

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...

problem is that name can be used to describe a store-path-name, a derivation-name, and a package-name ;(