| 31 Jan 2026 |
|  figsoda joined the room. | 20:22:49 |
| figsoda | Is there some way to specify the name of the output path when using nix flake prefetch or fetchTree? I digged a little through the source code, and it seems like name is an attribute that defaults to source and passed around, but I couldn't find any way to change it to something other than the default. | 20:27:47 |
 Sergei Zimmerman (xokdvium) | In reply to @figsoda:matrix.org
Is there some way to specify the name of the output path when using nix flake prefetch or fetchTree? I digged a little through the source code, and it seems like name is an attribute that defaults to source and passed around, but I couldn't find any way to change it to something other than the default. Don’t think so, it’s only allowed for fetchGit | 20:44:05 |
| Sergei Zimmerman (xokdvium) | FetchTreeParams::allowNameArgument | 20:44:24 |
| figsoda | Thanks for the pointers, do you know if there is a design reason why that's the case? Or is it just that they haven't got around to implementing it, and it was just there so fetchGit can use fetchTree | 20:48:11 |
| Sergei Zimmerman (xokdvium) | In reply to @figsoda:matrix.org
Thanks for the pointers, do you know if there is a design reason why that's the case? Or is it just that they haven't got around to implementing it, and it was just there so fetchGit can use fetchTree Honestly I don’t know. “source” is special-cases in all sorts of places in the store layer and the justification is probably along the lines of why that used to be preferred for FOD fetchers in nixpkgs - when changing the fetcher the outpath would stay the same. Whether that’s a good idea is another question | 20:50:09 |
| Sergei Zimmerman (xokdvium) | In reply to @figsoda:matrix.org
Thanks for the pointers, do you know if there is a design reason why that's the case? Or is it just that they haven't got around to implementing it, and it was just there so fetchGit can use fetchTree * Honestly I don’t know. “source” is special-cased in all sorts of places in the store layer and the justification is probably along the lines of why that used to be preferred for FOD fetchers in nixpkgs - when changing the fetcher the outpath would stay the same. Whether that’s a good idea is another question | 20:50:51 |
| figsoda | Thanks anyway, I'll probably open an issue later | 20:51:16 |
 eveeifyeve | Sergei Zimmerman (xokdvium): is it werid for a test to error out on my pr? Because I can't seem to debug the netrc isn't an absolute path thing. | 20:52:03 |
| eveeifyeve | https://github.com/NixOS/nix/pull/15041/ | 20:52:30 |
| eveeifyeve | * Sergei Zimmerman (xokdvium): is it werid for a test to error out on my pr? Because I can't seem to debug the netrc isn't an absolute path thing reproduced the test error locally, but I don't know where I can start to debug it. | 20:53:29 |
| Sergei Zimmerman (xokdvium) | Builtin builder does set it to a relative path apparently | 20:54:33 |
| eveeifyeve | Huh werid? | 20:55:56 |
| 1 Feb 2026 |
|  nathan0x28A joined the room. | 00:25:21 |
|  @leoflo:matrix.org joined the room. | 00:43:29 |
| @leoflo:matrix.org | Redacted or Malformed Event | 00:47:55 |
| @leoflo:matrix.org set a profile picture. | 00:54:42 |
