| 12 Jan 2026 |
 raitobezarius | in many reasonable software, an environment variable serves to seed an initial default | 18:48:32 |
| raitobezarius | there's 3 provenances for the setting system: NIX_CONF, the default settings file locations, -I | 18:49:07 |
| raitobezarius | and 1 provenance via env var: NIX_PATH | 18:49:12 |
|  isabel changed their profile picture. | 18:59:01 |
 John Ericson | snix should just not implement NIX_PATH I think | 19:55:37 |
| John Ericson | at least not like it currently exists | 19:55:41 |
| John Ericson | I do not wish that pain upon you all! :) | 19:56:09 |
 flokli | We don't have the luxury, at least the common / sensible usages should work | 19:56:17 |
| John Ericson | I thought snix was deprioritzing the evaluator as a whole? | 19:56:38 |
| flokli | Who said that? 😄 | 19:57:22 |
| John Ericson | a conservative NIX_PATH implementation would split on :, and require every entry to start with a / | 19:57:50 |
| John Ericson | just don't support URLs at all | 19:58:05 |
| John Ericson | and don't accidentally treat a URL as two valid relative paths | 19:58:27 |
| John Ericson | * and don't accidentally treat a URL as two valid relative path entries | 19:58:31 |
| John Ericson | (no foobar://x becomes foobar and ///x) | 19:59:12 |
| John Ericson | * (no foobar://x becomes foobar and //x) | 19:59:20 |
 Sergei Zimmerman (xokdvium) | Honestly I’m not even sure how URL parsing could in principle be implemented correctly. : can appear in the path component. There’s no way around the ambiguity. The alternative is to just accept colons have to be url encoded | 20:14:02 |
| Sergei Zimmerman (xokdvium) | * Honestly I’m not even sure how URL parsing could in principle be implemented correctly. : can appear in the path component. There’s no way around the ambiguity. The alternative is to just accept that colons have to be url encoded | 20:14:15 |
| Sergei Zimmerman (xokdvium) | And greedy matching here wouldn’t help too I think | 20:16:01 |
| flokli | https://github.com/gytis-ivaskevicius/high-quality-nix-content/raw/master/memes/nix-path-supports-urls.jpg | 20:32:42 |
 Ilan Joselevich (Kranzes) | This was posted already during this discussion 🤣 | 20:37:27 |
 SomeoneSerge (back on matrix) | Oooor we reserve the name "flakeref" and their syntax so that we can call them "legacy", and introduce the $scheme:// syntax for the flake-agnostic CLI. Then github:nixos/nixpkgs -> github://nixos/nixpkgs?flake=true or such, and the $scheme refers to a fetcher | 20:56:54 |
| raitobezarius | but you still need to come up with replacements to flakeref throughout the codebase like | 21:02:30 |
| raitobezarius | the concept of profiles relies on flakerefs | 21:02:42 |
| raitobezarius | if it melts into URLs and flakerefs are only a specific scheme of URLs, it's all fine | 21:02:52 |
| Sergei Zimmerman (xokdvium) | Don't you mean horrendous regexes and strings? | 22:16:31 |
| Sergei Zimmerman (xokdvium) | Ehhhhh, in this example nixos is the hostname | 22:16:56 |
| Sergei Zimmerman (xokdvium) | Not sure it's a good idea to be even more idiosyncratic than it already is | 22:18:08 |
| Sergei Zimmerman (xokdvium) | Also nix flake show github://aaaaaaaaaaaaaa/nixos/nix works nowadays both on lix and nix | 22:19:33 |
| Sergei Zimmerman (xokdvium) | The authority just gets ignored | 22:19:41 |
