| 1 |
"John R. Graham" <n3440d@×××××.com> posted 46F25716.4050608@×××××.com, |
| 2 |
excerpted below, on Thu, 20 Sep 2007 07:18:46 -0400: |
| 3 |
|
| 4 |
> But, hasn't anyone realized that bash is _broken_ if this file doesn't |
| 5 |
> exist? Quoting from the upstream-provided man page, "When an |
| 6 |
> interactive shell that is not a login shell is started, bash reads and |
| 7 |
> executes commands from ~/.bashrc, if that file exists." Is that really |
| 8 |
> the intention here? To break upstream-defined behavior? |
| 9 |
|
| 10 |
... "if that file exists." IOW, it doesn't /have/ to exist, and for |
| 11 |
root, many prefer it /not/ exist. |
| 12 |
|
| 13 |
But in any case, as mentioned by others already, (human user) home dirs |
| 14 |
shouldn't be touched by ebuilds (or stages), and /root is exactly that, a |
| 15 |
(human user) home dir. Home dirs are the domain of the local users and |
| 16 |
(particularly for /root) sysadmins, not distribution packages (or |
| 17 |
stages). If the sysadmin wants a /root/.bashrc, it's naturally his |
| 18 |
privilege and responsibility to create and maintain it according to his |
| 19 |
needs/preferences. |
| 20 |
|
| 21 |
-- |
| 22 |
Duncan - List replies preferred. No HTML msgs. |
| 23 |
"Every nonfree program has a lord, a master -- |
| 24 |
and if you use the program, he is your master." Richard Stallman |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives