On Thu, 5 Jan 2006, cobaco (aka Bart Cornelis) wrote: > What Side affects?
The file /etc/profile is similar to .profile, except that it is global. As a user, I would become very upset if installing a package would alter my $HOME/.profile. Whatever I do in my startup scripts is not a business of any package, it's my business as a user. Allowing /etc/profile.d would be the equivalent of allowing packages to modify the user's startup files. It would break the principle of least surprise, and therefore a bad thing. Moreover, dpkg usually asks about changes in configuration files in /etc. Having a profile.d would be the equivalent of dpkg being allowed to change /etc/profile without the user being prompted about the change. The principle of least surprise would be broken again. So no, I do not believe in legitimate uses of profile.d. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
