[gentoo-dev] Re: [gentoo-soc] Re: Progress on Universal Select Tool

["Sérgio Almeida" <mephx.x@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

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 git bisect. I would recommend that you try to do this,
> if only just to learn how to make good commits.
> 

Will try to do this from this state on. Starting this week.

> You could take a look at how the kernel folks handle this -- features
> go in as several small commits/patches.

Thanks, will surely look at it.



Now, a little call for help to everybody:

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

Reliable options:

* Spawn a child shell with the chosen environment
	os.execv('/bin/bash', []) # can be whatever shell

* Wrap uprofile into a /bin/whateversh script that changes environment
acording to what child uprofile says. Ugly stuff.

Unreliable options:

* gdb/similar attach to parent and do some "call"s
* wrap watheversh into something that supports env changes from child
processes

I like the first idea the most even though it's a sub-shell. This method
kind of breaks automatic startup of uprofile for HOME.

Anyone has a clue on this? Off to sleep...

Cheers,
Sérgio 
-- 
Sérgio Almeida - mephx.x@gmail.com
mephx @ freenode


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]