!SgYlXivkogarTVcnZO:nixos.org

Nix Flakes

885 Members
179 Servers

Load older messages


SenderMessageTime
21 Oct 2023
@thesola10:matrix.orgTheSola10 joined the room.09:50:58
@ngn999:matrix.org@ngn999:matrix.org changed their profile picture.12:45:23
@ngn999:matrix.org@ngn999:matrix.org changed their profile picture.12:46:03
@twitchy0:matrix.orgtwitchy0
In reply to @antifuchs:asf.computer
try github:pftf/RPi4/v1.35? That'll be the source tree with the tag v1.35
that worked, thanks! it doesn't have the release zip or its contents though. I just ended up using a derivation which worked
15:47:41
@antifuchs:asf.computer@antifuchs:asf.computer awesome, yeah that's the tradeoff: if you depend on a release upload, you can really only use fetchzip and such 15:48:18
@twitchy0:matrix.orgtwitchy0
In reply to @antifuchs:asf.computer
try github:pftf/RPi4/v1.35? That'll be the source tree with the tag v1.35
* that kinda worked, thanks! it doesn't have the release zip or its contents though. I just ended up using a derivation which worked
15:48:21
@rwx-rwx-rwx:matrix.orgMikael Fangel changed their display name from rwx-rwx-rwx to Mikael Fangel.17:15:37
@rwx-rwx-rwx:matrix.orgMikael Fangel set a profile picture.17:22:07
22 Oct 2023
@mokasin:mokasin.de@mokasin:mokasin.de changed their display name from Fabian to mokasin.16:12:13
@erazemk:matrix.org@erazemk:matrix.org joined the room.17:29:13
@globin:toznenetl.chatglobin joined the room.19:55:42
@janik0:matrix.org@janik0:matrix.org joined the room.21:03:21
@js:ukvly.orgJulian Stecklina (Old) joined the room.21:38:12
23 Oct 2023
@robin.gloster:matrix.mayflower.de@robin.gloster:matrix.mayflower.de left the room.09:49:12
@globin:toznenetl.chatglobin set a profile picture.14:27:35
24 Oct 2023
@streets_saucing:matrix.orgstreets joined the room.17:24:45
@greg:matrix.burd.meGreg Burd joined the room.19:51:53
@lorenzleutgeb:matrix.orgLorenz Leutgeb joined the room.20:06:59
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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
@pederbs:pvv.ntnu.nopbsds make an alias? 20:26:33
@pederbs:pvv.ntnu.nopbsds nix registry may be the place to look 20:26:57
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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
@pederbs:pvv.ntnu.nopbsdsYou use the resolved flake url in nix build20:53:01
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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
@lorenzleutgeb:matrix.orgLorenz 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

Show newer messages


Back to Room ListRoom Version: 6