I'd put that down to because you either didn't understand the consequences of running the command, or forgot you ran the command and so later on when things go weird, it causes confusion. -- e.g. for me, I initially had run `# nix-env -iA nixpkgs.firefox`; later, I was confused why firefox was installed, even though it wasn't installed in my profile at all.
I think the risks of `nix-env -i` are overstated, and over-repeated without explanation. Albeit, it is foot-gun-ish enough that it's worth at least echoing "nix community frowns upon its usage".
Re:Some Notes on Using Nix
by aerzen on Wednesday March 01, 2023 @05:39PM
(#34989333)
Great writeup - exactly my level of understanding of nix. I hope this gives insight to nix developers about where the potential for improvement of the package manager.
Re:Some Notes on Using Nix
by yakubin on Wednesday March 01, 2023 @11:27PM
(#34992018)
I wanted to use Nix on Mac, but the only supported setup is the one that puts a persistent daemon in the background, which just doesn't sit well with me for a package manager – something that I use maybe once a month, maybe even less. I don't understand why they didn't go with setuid.
> Devbox is a command-line tool that lets you easily create isolated shells for development
it uses nix, and they just added
`devbox global`
> Devbox Global allows you to add packages to a global devbox.json. This is useful for installing a standard set of tools you want to use across multiple Devbox Projects. You can also use Devbox Global to install and manage packages on your Host OS, as a substitute for tools like brew or apt-get.
The better way is to use nix-shell -p firefox.
Julia's write-up is terrific, otherwise.
I'd put that down to because you either didn't understand the consequences of running the command, or forgot you ran the command and so later on when things go weird, it causes confusion. -- e.g. for me, I initially had run `# nix-env -iA nixpkgs.firefox`; later, I was confused why firefox was installed, even though it wasn't installed in my profile at all.
I think the risks of `nix-env -i` are overstated, and over-repeated without explanation. Albeit, it is foot-gun-ish enough that it's worth at least echoing "nix community frowns upon its usage".
> Devbox is a command-line tool that lets you easily create isolated shells for development
it uses nix, and they just added
`devbox global`
> Devbox Global allows you to add packages to a global devbox.json. This is useful for installing a standard set of tools you want to use across multiple Devbox Projects. You can also use Devbox Global to install and manage packages on your Host OS, as a substitute for tools like brew or apt-get.
https://github.com/jetpack-io/devbox/releases/tag/0.4.0