| 21 Oct 2023 |
|  Mikael Fangel changed their display name from rwx-rwx-rwx to Mikael Fangel. | 17:15:37 |
| Mikael Fangel set a profile picture. | 17:22:07 |
| 22 Oct 2023 |
|  @mokasin:mokasin.de changed their display name from Fabian to mokasin. | 16:12:13 |
|  @erazemk:matrix.org joined the room. | 17:29:13 |
|  globin joined the room. | 19:55:42 |
|  @janik0:matrix.org joined the room. | 21:03:21 |
|  Julian Stecklina (Old) joined the room. | 21:38:12 |
| 23 Oct 2023 |
|  @robin.gloster:matrix.mayflower.de left the room. | 09:49:12 |
| globin set a profile picture. | 14:27:35 |
| 24 Oct 2023 |
|  streets joined the room. | 17:24:45 |
|  Greg Burd joined the room. | 19:51:53 |
|  Lorenz Leutgeb joined the room. | 20:06:59 |
| Lorenz Leutgeb | When exeucuting nix build github:NixOS/nixpkgs/nixos-unstable#hello I would like nix build to print the revision that it used (to have a reproducible copy-pastable output). There doesn't seem to be an option? How do I do that? | 20:08:33 |
| Lorenz Leutgeb | * When exeucuting nix build github:NixOS/nixpkgs/nixos-unstable#hello I would like nix build to print the revision that it used, i.e. the hash that "nixos-unstable" referred to at the time of invocation, (to have a reproducible copy-pastable output). There doesn't seem to be an option? How do I do that? | 20:23:57 |
| Lorenz Leutgeb | * When exeucuting nix build github:NixOS/nixpkgs/nixos-unstable#hello I would like nix build to print the revision that it used, i.e. the hash that "nixos-unstable" referred to at the time of invocation, to have a reproducible copy-pastable output. There doesn't seem to be an option? How do I do that? | 20:25:15 |
 pbsds | make an alias? | 20:26:33 |
| pbsds | nix registry may be the place to look | 20:26:57 |
| Lorenz Leutgeb | In reply to @pederbs:pvv.ntnu.no
nix registry may be the place to look I'd like a solution that works both for flakes that are in the registry and for ones that are not. The requirement to know which revision was used isn't that crazy, is it? | 20:27:54 |
| Lorenz Leutgeb | In reply to @pederbs:pvv.ntnu.no
nix registry may be the place to look * I'd like a solution that works both for flakes that are in the registry and for ones that are not. The question which revision was used isn't that crazy, is it? | 20:28:03 |
| Lorenz Leutgeb | In reply to @pederbs:pvv.ntnu.no
make an alias? You mean a shell alias? An alias from what to what? I don't know an that gives me the output I want. I could call nix flake show right before/after I call nix build, but that's racy. | 20:30:00 |
| pbsds | You use the resolved flake url in nix build | 20:53:01 |
| Lorenz Leutgeb | One nice property of flakes is that I can address them as github:edolstra/hello, that's something I can remember as a human. This reference changes over time and is not reproducible. Whenever I call nix build github:edolstra/hello, Nix must inevitably somehow resolve this reference to a concrete revision. The concrete revision is a long hexadecimal string I cannot remember. Therefore I do see value in nix build to, when requested, just print the revision. Then, I can share its output (which now includes the resolved URL, which includes the hash) to my teammates, who can run the same build even if the revision that the default branch of github:edolstra/hello resolves to has changed in the meantime.
It's not a question of whether there is a possibility to somehow obtain a fully resolved flake URL, and that it can be provided as an argument to nix build, but a matter of convenience of the user experience with nix build.
| 20:58:37 |
| Lorenz Leutgeb | * One nice property of flakes is that I can address them as github:edolstra/hello, that's something I can remember as a human. This reference changes over time and is not reproducible. Whenever I call nix build github:edolstra/hello, Nix must inevitably somehow resolve this reference to a concrete revision. The concrete revision contains a long hexadecimal string I cannot remember. Therefore I do see value in nix build to, when requested, just print the revision. Then, I can share its output (which now includes the resolved URL, which includes the hash) to my teammates, who can run the same build even if the revision that the default branch of github:edolstra/hello resolves to has changed in the meantime.
It's not a question of whether there is a possibility to somehow obtain a fully resolved flake URL, and that it can be provided as an argument to nix build, but a matter of convenience of the user experience with nix build.
| 20:58:59 |
| Lorenz Leutgeb | * One nice property of flakes is that I can address them as github:edolstra/hello, that's something I can remember as a human. This reference changes over time and is not reproducible. Whenever I call nix build github:edolstra/hello, Nix must inevitably somehow resolve this reference to a concrete revision. The concrete revision contains a long hexadecimal string I cannot remember. Therefore I do see value in nix build to, when requested, just print the revision, i.e. the result of the resolution it must perform anyways. Then, I can share its output (which now includes the resolved URL, which includes the hash) to my teammates, who can run the same build even if the revision that the default branch of github:edolstra/hello resolves to has changed in the meantime.
It's not a question of whether there is a possibility to somehow obtain a fully resolved flake URL, and that it can be provided as an argument to nix build, but a matter of convenience of the user experience with nix build.
| 20:59:27 |
| Lorenz Leutgeb | nix flake show does this by the way (as I have mentioned above), but there's no way for me to guarantee that the reference does not change in between invocations of nix build and nix flake show. That's why I am asking for a solution that only involves nix build. Or a convincing explanation for a better solution... | 21:03:38 |
| pbsds | huh, you're right | 21:06:42 |
| pbsds | there is no utility to expand github:nixos/nixpkgs#hello to e.g. github:NixOS/nixpkgs/7e63eed145566cca98158613f3700515b4009ce3#hello | 21:07:26 |
| Lorenz Leutgeb | At least I couldn't find one... And if there would be one, I'd still prefer nix build to give me the expansion of the very thing I am building to avoid races (colleague pushing to Git in parallel, who knows...). | 21:08:24 |
| Lorenz Leutgeb | * At least I couldn't find one... And if there would be one, I'd still prefer nix build to give me the expansion of the very thing I am building to avoid races (colleague pushing to Git host in parallel, who knows...). | 21:08:45 |
| Lorenz Leutgeb | Also note that nix flake show --json does not print the resolved URL (which nix flake show does). I just filed an issue: https://github.com/NixOS/nix/issues/9230 | 21:09:44 |
