| 12 Jan 2026 |
roberth | :( | 18:43:22 |
raitobezarius | well, if you put a flakeref in a NIX_PATH, it doesn't require an xp feature | 18:43:31 |
raitobezarius | but at the boundary, an xp feature will be required | 18:43:35 |
roberth | it damn well should have... | 18:43:47 |
raitobezarius | it doesn't matter much in the end | 18:44:06 |
raitobezarius | flakerefs are theoretically experimental | 18:44:18 |
raitobezarius | in practice, breaking backward compat of it is not a good idea | 18:44:31 |
roberth | they're already part of the sediment record | 18:44:40 |
raitobezarius | flakerefs as a term should die | 18:44:46 |
raitobezarius | and we should all pretend they are actually URLs | 18:44:52 |
raitobezarius | there, they're not about flakes anymore | 18:45:00 |
roberth | I've called them sourcerefs occasionally when talking about fetchTree | 18:45:33 |
roberth | flakref = sourceref + ?dir | 18:45:49 |
Sergei Zimmerman (xokdvium) | And also git's URL (but I think nowadays nix doesn't actually support some of these cuz fetchTree) is a huge mess too. Just ran into:
GIT_TRACE=1 git clone "xokdvium@[localhost]hahahahahahhahaha:/~/work/code/nix"
| 18:46:09 |
Sergei Zimmerman (xokdvium) | Any bets if this works or not? | 18:46:16 |
Sergei Zimmerman (xokdvium) | * And also git's URL (scp-like paths they call these) (but I think nowadays nix doesn't actually support some of these cuz fetchTree) is a huge mess too. Just ran into:
GIT_TRACE=1 git clone "xokdvium@[localhost]hahahahahahhahaha:/~/work/code/nix"
| 18:47:04 |
Ilan Joselevich (Kranzes) | is -I supposed to behave differently of NIX_PATH? | 18:47:21 |