On Mon, 2009-07-27 at 10:33 +0200, Michael Haubenwallner wrote:
>
> I'd say leave it to the user to either use the CHANGEDIR event,
> or define some alias like 'ucd', or call 'uprofile' manually only.
> Eh - provide an uselect-module to select the variant...
>
Never though of that... Nice idea!
Sérgio Almeida wrote:
> On Fri, 2009-07-24 at 10:22 +0200, Michael Haubenwallner wrote:
>>> if cmd = 'chdir':
>>> uprofile
>> ..., the automatism for the 'cd' command feels like more
>> confusing than useful...
> Atm, cd just changes dir as it is supposed to. Robert alerted us to the
> fact
On Fri, 2009-07-24 at 10:22 +0200, Michael Haubenwallner wrote:
> Sérgio Almeida wrote:
> > 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
Sérgio Almeida wrote:
> 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.
..., change back to your home dir, call uprofile, and you have y
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
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
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
>
I don't understand what use this feature has. Won't the "current
pro
Hello,
On Thu, 2009-07-23 at 08:39 +0530, Nirbheek Chauhan wrote:
> It's probably wise to commit code in small-ish (and self-containing)
> discrete units each of which add something without breaking anything.
> Otherwise, it becomes very difficult to track down which change broke
> something via g
2009/7/23 Sérgio Almeida :
> I'm still not doing any commits as uselect can still break your python
> environment while testing and i don't have the time to learn how to
> handle branches in git.
>
It's probably wise to commit code in small-ish (and self-containing)
discrete units each of which ad
Sebastian,
> It seems to me that the original langauge is "static"/"descriptive"
> while Python is not. Why not move to XML or JSON (former seems more
> common with Gentoo) instead of Python? Think about how much easier it
> is to pull information from metadata.xml than from .ebuild files - it's
Sérgio Almeida wrote:
> user action bin {
> description "Change Python's Version"
> type sym
> sym python {
> bin python
> target /usr/bin/python
> prefix /usr/bin/
> regexp python([0-9]+\.[0-9]+$)
> sym pytho
13 matches
Mail list logo
