4 ms·
I don't understand the point of creating an entirely new shell inheriting almost nothing. Seems like that would cause a lot of issues (i.e., sudo make install)
by withinboredom 3y ago
I don't understand the point of creating an entirely new shell inheriting almost nothing. Seems like that would cause a lot of issues (i.e., sudo make install)
- Arnavion 3y agoThat's how sudo already works on most (all?) distros. Eg Debian 12 has: Defaults env_reset ... which will clear almost everything that `make install` would've used. OpenSUSE TW has: Defaults always_set_home Defaults env_reset Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE" ... which is a lot more, but will still clear whatever `make install` would've used. Anything you need to give to `make install` should be given explicitly, like `sudo make INSTALL_ROOT=$INSTALL_ROOT install` or whatever.
- gcbirzan 3y agoIf you're using autoconf/automake, you don't need to do that.