From: Herbert Fischer <herbert.fischer@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] /etc/profile.d/
Date: Sat, 16 Jul 2005 15:08:12 -0300 [thread overview]
Message-ID: <9f90e8bf0507161108656f8747@mail.gmail.com> (raw)
In-Reply-To: <9f90e8bf0507161037b580c07@mail.gmail.com>
I meant... Isn't this directory subject to developers installing
custom .bashrc or .bash_profile, or whatever automatically executed on
login?
On 7/16/05, Herbert Fischer <herbert.fischer@gmail.com> wrote:
> So... why /etc/.skel/ needs to be touched by Gentoo emerges? Isn't
> this directory subject to developers installing foo-bar.sh files?
>
> So, isn't this case the same with /etc/profile.d ??
>
> On 7/16/05, Marius Mauch <genone@gentoo.org> wrote:
> > On Fri, 15 Jul 2005 21:34:09 -0400
> > Mike Frysinger <vapier@gentoo.org> wrote:
> >
> > > we could care less what users do with /etc/profile.d ... the point is
> > > that *only* users should use /etc/profile.d ... we dont want random
> > > Gentoo developer Foo installing some Bar.sh into /etc/profile.d with
> > > package app-crap/FooBar
> >
> > Would the following in /et/profile be a solution to this problem?
> >
> > for x in $( < /etc/profile.d/.default); do
> > source "/etc/profile.d/${x}"
> > done
> >
> > That way devs could install stuff there, but it would only be run if
> > users added it to the .default file.
> >
> > Marius
> >
> > --
> > Public Key at http://www.genone.de/info/gpg-key.pub
> >
> > In the beginning, there was nothing. And God said, 'Let there be
> > Light.' And there was still nothing, but you could see a bit better.
> >
> >
> >
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-16 18:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 21:59 [gentoo-dev] /etc/profile.d/ Herbert Fischer
2005-07-15 22:11 ` Mike Frysinger
2005-07-15 22:36 ` Herbert Fischer
2005-07-15 22:41 ` Mike Frysinger
2005-07-15 22:56 ` Herbert Fischer
2005-07-15 23:02 ` Mike Frysinger
2005-07-15 23:40 ` Herbert Fischer
2005-07-16 1:25 ` Michael Marineau
2005-07-16 1:34 ` Mike Frysinger
2005-07-16 1:56 ` Michael Marineau
2005-07-16 2:03 ` Mike Frysinger
2005-07-16 3:03 ` Donnie Berkholz
2005-07-16 17:03 ` Marius Mauch
2005-07-16 17:37 ` Herbert Fischer
2005-07-16 18:08 ` Herbert Fischer [this message]
2005-07-16 18:24 ` Herbert Fischer
2005-07-17 0:21 ` Mike Frysinger
2005-07-16 20:58 ` Martin Schlemmer
2005-07-17 0:23 ` Mike Frysinger
2005-07-17 0:22 ` Mike Frysinger
2005-07-17 2:38 ` Marius Mauch
2005-07-17 2:48 ` Mike Frysinger
2005-07-18 6:53 ` Donnie Berkholz
2005-07-18 13:00 ` Mike Frysinger
2005-07-18 23:47 ` Donnie Berkholz
2005-07-19 0:00 ` Mike Frysinger
2005-07-19 0:10 ` Donnie Berkholz
2005-07-20 19:27 ` Herbert Fischer
2005-07-20 21:05 ` Mike Frysinger
2005-07-20 22:46 ` Herbert Fischer
2005-07-20 22:52 ` Mike Frysinger
2005-07-20 23:26 ` Herbert Fischer
2005-07-16 16:51 ` Herbert Fischer
2005-07-16 3:16 ` Aaron Walker
2005-07-17 0:24 ` Mike Frysinger
2005-07-17 1:13 ` Herbert Fischer
2005-07-17 1:18 ` Mike Frysinger
2005-07-17 11:35 ` [gentoo-dev] /etc/profile.d/ Duncan
2005-07-16 10:40 ` [gentoo-dev] /etc/profile.d/ Martin Schlemmer
2005-07-16 5:46 ` Petteri Räty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f90e8bf0507161108656f8747@mail.gmail.com \
--to=herbert.fischer@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox