Re: [gentoo-dev] Portage Toys

[Marius Mauch]

On 10/06/04  Ned Ludd wrote:

> On Wed, 2004-10-06 at 18:53, Jason Stubbs wrote:
> > On Thursday 07 October 2004 06:29, Michael Tindal wrote:
> > > On Wed, 2004-10-06 at 19:57 +0900, Jason Stubbs wrote:
> > > > On Wednesday 06 October 2004 12:09, Michael Tindal wrote:
> > > > > The format is something like
> > > > > category/pkgname
> > > > > CFLAGS="...";LDFLAGS="...";USE="...";FEATURES="..."
> > > >
> > > > Unless you like things not compiling due to missing
> > > > dependencies, don't use USE in this file. Same deal with
> > > > ACCEPT_KEYWORDS and anything else that could possibly affect
> > > > dependencies (which is nothing that I can think of at this
> > > > stage).
> > >
> > >  That wasn't really the point of the exercise (USE and the like).
> > > Portage already has files for that, so using this for that is
> > > pointless. It was more for CFLAGS and LDFLAGS and such, and the
> > > example I gave was off the top of my head.
> >
> > No problem. I was mostly just pointing it out for the onlookers and
> > to preempt invalid bug reports. Also worth pointing out is that most
> > FEATURES would not be honoured as well, as bashrc is only used on
> > the bash side of things whereas the python side of portage handles
> > most of them.
>
> Portage learns about FEATURES after it's sourced the ebuild in the
> depend phase right?
> If so then it would seem that those functions-FEATURES/USE which have
> todo with depgraph creation could be exported in the 'depend' phase
> from a bashrc. Is my logic incorrect?

Yes. The variables that affect the python side (which includes depgraph
stuff) come from the portage.config class which is initialized when
'import portage' is called. Also ebuild.sh (including your bashrc) is a
subprocess of emerge (including portage.py and the config class) and to
my knowledge you can't just export env-variables to the parent process,
so you'd need a more advanced communication.

Marius