>[...] it can’t define which environment variables should be available in the developer shell or which hooks to run upon entry. Neither pacman, apt, nor any ot

>[...] it can’t define which environment variables should be available in the developer shell or which hooks to run upon entry. Neither pacman, apt, nor any other package manger require any sort of virtualization. pacman works fine where-ever you have a C compiler including macos, linux, windows, probably even TempleOS. Whatever you want. If you want to add something to the user environment system wide, the traditional thing to do is to dump a file into `/etc/profile.d/` which will be sourced during shell startup. If you instead want something local to the project, you just make a script that the developer can source, like a python virtualenvironment. I'm not saying any of these ideas are bad. I am saying that they are easily solvable and have been solved for the past 20 years. Without Nix.