Re: [gentoo-alt] Having a persistent bash environment variable

[Alan Hourihane]

On Mon, 2008-02-04 at 21:45 +0100, Fabian Groffen wrote:
> On 04-02-2008 19:48:28 +0000, Alan Hourihane wrote:
> > > > > Do I understand correctly if I say that you set UNIXMODE in your
> > > > > environment, call portage and that you find that the
> > > > > compilation/installation doesn't seem to have UNIXMODE set?
> > > >
> > > > Yes. I've fixed this currently with adding
> > > >
> > > > export UNIXMODE=....
> > > >
> > > > at the top of ebuild.sh
> > >
> > > Ok, that's a crude hack, I'll ask around to see how we can do this
> > > properly.
> >
> > Right, please do, I'd love to hear the correct solution.
>
> Could you add the following to your etc/portage/bashrc:
>
> echo EBUILD_PHASE=${EBUILD_PHASE} UNIXMODE=${UNIXMODE}
>
> Remove your hack and set UNIXMODE in etc/make.conf
>
> Then run portage, and check if the var is set.  Also, during
> compilation, it should be stored in the environment file in the "temp"
> dir of your var/tmp/portage/cat/pkg/.

O.k. it is there on the echo, but something is removing it in the
ebuild.sh script as it's failed again. I'm pretty sure it's the
filter_readonly_variables() doing it, then it puts it back when it
sources the environment later. 

But that's too late, because if UNIXMODE is removed I lose, and sed
breaks.

Alan.

-- 
gentoo-alt@l.g.o mailing list