"John R. Graham" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Thu, 20 Sep 2007 07:18:46 -0400:
> But, hasn't anyone realized that bash is _broken_ if this file doesn't > exist? Quoting from the upstream-provided man page, "When an > interactive shell that is not a login shell is started, bash reads and > executes commands from ~/.bashrc, if that file exists." Is that really > the intention here? To break upstream-defined behavior? ... "if that file exists." IOW, it doesn't /have/ to exist, and for root, many prefer it /not/ exist. But in any case, as mentioned by others already, (human user) home dirs shouldn't be touched by ebuilds (or stages), and /root is exactly that, a (human user) home dir. Home dirs are the domain of the local users and (particularly for /root) sysadmins, not distribution packages (or stages). If the sysadmin wants a /root/.bashrc, it's naturally his privilege and responsibility to create and maintain it according to his needs/preferences. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
