On Thu, 2009-07-23 at 17:28 +0200, Robert Buchholz wrote:
> On Thursday 23 July 2009, Sérgio Almeida wrote:
> > You changedir, you call uprofile, and
> > voila, new profile. You login again, default profile.
>
> Most shells have the ability to execute a command when a new prompt is
> generated. U
On Thursday 23 July 2009, Sérgio Almeida wrote:
> You changedir, you call uprofile, and
> voila, new profile. You login again, default profile.
Most shells have the ability to execute a command when a new prompt is
generated. Users do not need to call uprofile themselves, they could
set up their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 23 Jul 2009 03:06:36 +
"Jorge Manuel B. S. Vicetto" wrote:
> Does everyone using the desktop profile really need all of the
> following?
Not the question to be asking. The question to ask is, for those people
who use packages where those
On Thu, 2009-07-23 at 13:17 +0530, Arun Raghavan wrote:
> 2009/7/23 Nirbheek Chauhan :
> > 2009/7/23 Sérgio Almeida :
> >> A child process cannot (or shouldn't be able to) change parent's process
> >> environment.
> >>
> >> uprofile will need to change env var's on-the-fly. For instance tag $PS1
>
On Thu, 2009-07-23 at 11:02 +0530, Nirbheek Chauhan wrote:
> 2009/7/23 Sérgio Almeida :
> > A child process cannot (or shouldn't be able to) change parent's process
> > environment.
> >
> > uprofile will need to change env var's on-the-fly. For instance tag $PS1
> > with the current profile in use
El jue, 23-07-2009 a las 03:06 +, Jorge Manuel B. S. Vicetto
escribió:
> Please don't.
> Instead of having an ever larger collection of default use flags in the
> desktop profile, we should be taking advantage of EAPI-1 IUSE defaults
> and EAPI-2 use dependencies.
It's other way to go, of cour
