Re: pseudo interaction issue

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2012-03-26 at 02:43 -0500, Peter Seebach wrote:
> On Sat, 24 Mar 2012 17:15:15 +0000
> Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> > This implies that once we enable pseudo for a child, there is some
> > change in the parent which persists.
> 
> Hmm.
> 
> Is the parent running with pseudo loaded?  If it were, then I would
> expect this -- pseudo does some environment magic that can affect the
> parent, and also cause it to stash values for later restoration.

BitBake always runs with pseudo loaded but disabled. When we fork a
child, we decide whether to enable it or not and setup the environment
to either bring pseudo to life, or unload it from memory entirely.

It sounds to me like our enable/disable code confuses the heck out of
pseudo in the parent environment, likely overwriting a stashed value
which it needs to be able to find itself again (prefix/localstate).

Obviously we can change the way we manipulate the environment although
that isn't entirely straightforward as we need to ensure the pseudo
paths don't leak into sstate package checksums for example.

Cheers,

Richard