6 ms·
Yeah, the you would just do a quick `nix-shell -p <package>` and of you go. Much quicker than a `brew install` for me.
by fesc 5y ago
Yeah, the you would just do a quick `nix-shell -p <package>` and of you go.
Much quicker than a `brew install` for me.
- sontek 5y agoBut I don't want it temporarily, I want it all the time. So I want to be able to make it available for future me too, that way next time I try to use it I don't have to run `nix-shell -p <package>` again
- fesc 5y agoThen I would look into home-manager and/or nix-darwin if you are on macOS. I think under the hood home-manager basically declaratively manages a Nix profile for you. You (or even better a home-manager managed .bash_profile) can then put that profile into your PATH.
- colordrops 5y agoIt will still be on your system until garbage collected, so if you decide to install permanently, it will be instantaneous. "Permanent" is a fuzzy concept with Nix in any case, as all it means here is that it's in your path and won't be garbage collected. In this case you just add the package name to an array in your config. It's extremely simple to do, just editing a list in a text file. I understand you want to just run a command, but perhaps Nix is not for you if easy command line usage is more important than automated reproduceable OS config. That being said, I think there are indeed ways to partially manage your config using simple command line commands but I haven't found the need myself.