On Fri, 2008-02-01 at 21:58 +0100, Fabian Groffen wrote: > On 01-02-2008 20:37:23 +0000, Alan Hourihane wrote: > > On Fri, 2008-02-01 at 20:42 +0100, Fabian Groffen wrote: > > > On 01-02-2008 19:37:18 +0000, Alan Hourihane wrote: > > > > What's the best way to have a bash environment variable persist across > > > > an emerge ?? > > > > > > > > I've seen the ebuild.sh which filters out bash read only variables, and > > > > I've tried inserting mine into that list, but it doesn't seem to work. > > > > > > While I think this is mainly a Portage related question, still can you > > > explain why you want/need to do this? Or what you want to achieve? > > > > Because the libc I'm using read's an environment variable to determine > > functionality, and the emerge process is removing it and changing the > > way libc reacts. > > Feels like we need to know which environment variable this is and add it > to Portage's lists.
It's called UNIXMODE. But where do I add it in Portage's list ?? Alan. -- [email protected] mailing list
