Nix Flakes | 888 Members | |
| 178 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Oct 2021 | ||
| cdepillabout: This is an error internal to Nix. | 07:42:10 | |
Nix uses git internally when fetching Git repositories. | 07:42:18 | |
| * cdepillabout: This is a warning internal to Nix. | 07:42:55 | |
| I think this message is gone on master, see https://github.com/NixOS/nix/pull/4573 | 07:52:19 | |
| 10:38:26 | ||
| 10:44:51 | ||
In reply to @niksnut:matrix.orgAh great, thanks! | 11:07:55 | |
| 20:34:49 | ||
| 7 Oct 2021 | ||
| 09:41:19 | ||
| 8 Oct 2021 | ||
| nix now fetches submodules by default for flakes and I was wondering what would be the best way to expose all submodules for isolated use in the flake? My use case would be that in some cases, I just want my flake output on submodules, so I do not end up rebuilding them for all repo changes. | 09:01:50 | |
| * nix now fetches submodules by default for flakes and I was wondering what would be the best way to expose all submodules for isolated use in the flake? My use case would be that in some cases, I just want my flake ouput only depends on some submodules, but I do end up rebuilding for all repo changes. | 09:07:46 | |
| Florian | W3F - OoO Mon/Tue: Pretty sure that was reverted due to various issues. | 11:09:40 | |
| 13:50:55 | ||
| 15:14:01 | ||
| 10 Oct 2021 | ||
| I want to have packages in my flake.nix, and make them easily available as an overlay without repeating myself. The easiest way to do that is to expose the overlay and then a function that returns and overlaid nixpkgs, and then returning your packages from that set | 02:23:47 | |
| but how do you know the names of the packages to return in the packages attribute without duplicating? I guess I could instansiate the overlay with fake nixpkgs and then see what attrNames | 02:24:34 | |
| * but how do you know the names of the packages to return in the packages attribute without duplicating? I guess I could instansiate the overlay with fake nixpkgs and then see what the attrNames and filter on those. sounds tedious. | 02:24:45 | |
| You you just call the overlay function with fake parameters and then use attrNames on that? It won't need to evaluate the attr values so it won't error right? | 04:55:43 | |
Like attrNames (myOverlay null null). Not sure if that would work. Also it would be more complicated if you have package sets | 04:57:03 | |
| * Maybe you can call the overlay function with fake parameters and then use attrNames on that? It won't need to evaluate the attr values so it won't error right? | 04:59:35 | |
colemickens 🏳️🌈: builtins.attrNames (overlay null null) | 12:15:28 | |
| Is there some reason why flakes don't "discover" the It's annoying that | 23:16:15 | |
| * Is there some reason why flakes don't "discover" the It's annoying that | 23:16:16 | |
Like, I feel it's pretty common for tools (e.g. Cargo) to just go upwards into the Git repo looking for the build file (e.g. Cargo.toml) | 23:16:48 | |
| 12 Oct 2021 | ||
In reply to @colemickens:matrix.orgMy overlays often just returns all packages in a separate attrset, that I then return as packages.<system> = pkgs.<flake-name>. | 13:33:42 | |
Or you could just parameterize your overlay.nix to either return an overlay or a package attrset. | 13:34:39 | |
In reply to @Las:matrix.orgI have to look this up. Personally I would increase source control integration in nix. | 13:36:59 | |
In reply to @Las:matrix.org* To bad, personally I would increase source control integration of nix. | 13:37:51 | |
| colemickens 🏳️🌈: There is also flake-utils-plus | 13:50:09 | |
| 13 Oct 2021 | ||
| #5112 is soul-crushing | 00:04:48 | |