@zimbatm I see you had the same idea as me :) https://github.com/zimbatm/nix-path … vs https://github.com/imsl/nix-path
I've moved away from using NIX_PATH now though. I pass around paths explicitly now instead: https://github.com/evidentiae/infranix/blob/master/lib/eval-paths-module.nix …, a bit similar to https://nmattia.com/posts/2019-01-15-easy-peasy-nix-versions.html … (@nasmattia)
-
-
Great mind and all :) It's not obvious from the project name but it's designed to also handle explicit path injection: https://github.com/zimbatm/nix-path/blob/master/shell.nix#L2 … . I want the tool to handle all the use-cases: * NIX_PATH for legacy * eval-time fetches (for imports) * build-time fetches (for src)
-
The most important part of the project is to design flexible interfaces for the fetcher and updaters so they are easily extensible and handle all the use-cases in a uniform way.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.