On Wed, 6 Jul 2011, Georgios M. Zarkadas wrote: > I don't know if letting /etc/bash.bashrc to be sourced even on the > sh case has been done deliberately, but IMHO is not good, since code > in /etc/bash.bashrc typically assumes that the full bash featureset > is available, which is this case is a wrong assumption.
It's not done deliberately, it's just that this is subtle enough that no one has noticed it until now. Will be fixed in the next upload. I see that you are also trying to define a "sane" PS1 if bash.bashrc does not exist. I decided not to apply that part of the patch because if bash.bashrc does not exist, then I can assume that the user removed or modified it, in which case it is up to the user (i'd like to keep /etc/profile as short as possible). > If that kind of site-wide customisation is desired for sh shells it would be > better to be implemented as an `ENV=/etc/sh.shrc ; export ENV' sequence of > commands for the general sh case (so that it is also available for dash and > possibly other shells). I attach a supplementary patch for that, in case you > find this possibility of interest (etc_profile-sh.shrc.patch). I think this is more or less what /etc/profile.d is for. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
