From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google SoC @ Gentoo - Universal Select Tool
Date: Tue, 12 May 2009 18:34:38 +0200 [thread overview]
Message-ID: <1242146078.9407.13.camel@sapc154.salomon.at> (raw)
In-Reply-To: <1242138772.3438.74.camel@thedude>
On Tue, 2009-05-12 at 15:32 +0100, Sérgio Almeida wrote:
> > On Mon, 2009-05-04 at 22:01 +0100, Sérgio Almeida wrote:
> > > Here are the main interest ideas:
> > > * actions can be run system-wide and per-user:
> > > # action user moo
> > > # action system moo
> >
> > Are there any thoughts to support something more fine granular settings
> > than system and user?
>
> Indeed, user is not "for all the users". It's an action that can be run
> by the users to change it's own settings without touching the system's
> fallback default.
Seems you didn't really understand my problem yet - another try:
The *one* and *same* user does need different settings at the *same*
time depending on the project he's currently working on in different
shells. The actual setting needs to be set up by the project's
environment script (when the users enters the project), not the user's
profile script (when the user logs in).
> That's the point of the uselect tool. Per-System settings, Per-User
> settings (2 different ssh sessions of the same user can still have
> different environment settings too).
This maybe is what I'm after: Question still is how to easily set up the
different environment?
> I work as a sysadmin and manage mainly multi-user gentoo environments
> where people develop calculus c/python/fortran/R/whatever code using
> wathever utilities we can imagine. Everytime a new project is beeing
> done people need to set the environment variables themselves when they
> are kind enough not to ask me. That's mainly the whole purpose of this
> uselect tool, easy multi user environments managing.
Seems like we have a similar job ;)
Maybe it's the wording only, but in addition to the multi-user dimension
I'm still missing the multi-project dimension for one user.
/haubi/
--
Michael Haubenwallner
Gentoo on a different level
next prev parent reply other threads:[~2009-05-12 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 21:01 [gentoo-dev] Google SoC @ Gentoo - Universal Select Tool Sérgio Almeida
2009-05-05 2:30 ` Denis Dupeyron
2009-05-10 22:56 ` Mark Loeser
2009-05-11 19:09 ` Sérgio Almeida
2009-05-12 8:40 ` Michael Haubenwallner
2009-05-12 14:32 ` Sérgio Almeida
2009-05-12 16:34 ` Michael Haubenwallner [this message]
2009-05-12 20:45 ` Sérgio Almeida
2009-05-13 7:28 ` Michael Haubenwallner
2009-05-13 15:40 ` Sérgio Almeida
2009-05-15 11:08 ` Michael Haubenwallner
2009-05-23 2:18 ` Sérgio Almeida
2009-05-26 20:04 ` Tiziano Müller
2009-05-26 20:47 ` Sérgio Almeida
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=1242146078.9407.13.camel@sapc154.salomon.at \
--to=haubi@gentoo.org \
--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