Nix Flakes | 879 Members | |
| 175 Servers |
| Sender | Message | Time |
|---|---|---|
| 5 Oct 2021 | ||
| oh the fix i'm trying to get is actually a patch to stdenv | 18:55:37 | |
| installing a different stdenv seems like it would require rebuilding the world. hmm | 18:56:37 | |
| https://github.com/NixOS/nixpkgs/pull/138334/files | 18:56:58 | |
| 18:59:02 | ||
| 6 Oct 2021 | ||
| well, I called it with the registry | 05:17:30 | |
| but I guess I'm not enterprise enough, some people seem really into it | 05:18:05 | |
In reply to @colemickens:matrix.orgI feel called out :D | 05:18:21 | |
| I feel it's really convinient for managing a lot of repositories with overlapping dependencies, though | 05:19:01 | |
| I don't understand what you can do with it that you can't do with "..follows" other than specifically introduce machine or other-place indirection. Or why that property is helpful other than confusion the confusion shown earlier. | 06:51:00 | |
| When I run
Any idea why I would be getting this message when running Strangely enough, if I immediately exit out of the shell and run I guess it is possible that this is caused by calling | 07:31:51 | |
| 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 | |