Should we implement a /etc/profile.d?
- To: Debian Developers <firstname.lastname@example.org>
- Subject: Should we implement a /etc/profile.d?
- From: Nicolás Lichtmaier <nick@Feedback.com.ar>
- Date: Thu, 1 May 1997 11:21:50 -0300 (ARST)
- Message-id: <Pine.LNX.3.96.970501111440.301A-100000@localhost>
I think that we should. But we also have to think about this just as a
way to have nice defaults, I mean: We shouldn't worry too much about this.
Modifying login or such utilities for this I think it's a BAD idea.
I think we should just use the ". /etc/profile.d/*" approach. If somebody
uses a shell that doesn't allow environment variable declaration in a
standard/posic way... then that user is probably somebody that can live
without this feature. I mean: I will be satisfied if it works with bash,
ash, zsh (and probably the other flavours I don't know much about... csh?
ksh? do they declare variables like sh-clones?).
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .