| Please note that policy says: | | A program must not depend on environment variables to get reasonable | defaults. | | The way I read this, whatever "good" defaults you think should be in | /etc/profile, should be instead coded in the shells themselves | as a default when no PS1 is set at all.
The quote has no relevance in this point, because program's behavior is not dependent on it. There is a setting for bash, and a good default. If that were suddenly changed to '$ ', people would be very upset. | Please think about a way to follow policy which does not involve | making /etc/profile larger and larger. That's the wrong way. I do not believe policy saying that things must not grow and evolve over time, when there is are better ways to do things. Considerations: 1) The current /etc/profile is inefficient: it uses two processes to detect root user => That's a bug, which when fixed, the result is more efficient and implemts better code/variable reuse. 2) Defaults are provided for bash, so defaults should be provided equally to other shells too. Userss expect reasonable defaults when the system is installed. 3) Keeping things small has nothing to do with good and modular and good design. Even many lines of code can be simple to undestand ana manage when designed well. Exim4's split design is a fine example. | The right fix for this "bug" might involve removing lines from the | current /etc/profile, and that's the only reason why I'm going to keep | it open. What's the purpose of etc/defaults? This really should be brought to a wider discusson, since the position presented, that /etc/profile should be cleaned does not serve Debian users. The system should serve the people and provide out of the box reasonable and expected defaults without having to tinker immediately anything, so the /etc/profile should be utilized in its full potential. It should not become an obstacle. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
