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
