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

[Fabian Groffen]

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/.

> I'm using portage-prefix 9233 currently with bash 3.2(0) and tried
> 3.2(33), although I believe anything higher than (20) triggers the usual
> problems.

Those versions should be ok, I think...

> > > How do I go about sending patches in to get into the tree so I don't
> > > lose the current patches when I do an emerge --sync ??
> >
> > The tree is an svn tree, so no changes in the tree will be lost.  Your
> > change in ebuild.sh will get lost as soon as you update portage.
>
> O.k. I can deal with the ebuild.sh modification for now until we get a
> more definitive answer.
>
> What about changes to the bootstrap-prefix.sh ?

It is also in the svn tree, so also there svn will retain your changes.


-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-alt@l.g.o mailing list