| 1 |
On Fri, 2008-02-01 at 21:58 +0100, Fabian Groffen wrote: |
| 2 |
> On 01-02-2008 20:37:23 +0000, Alan Hourihane wrote: |
| 3 |
> > On Fri, 2008-02-01 at 20:42 +0100, Fabian Groffen wrote: |
| 4 |
> > > On 01-02-2008 19:37:18 +0000, Alan Hourihane wrote: |
| 5 |
> > > > What's the best way to have a bash environment variable persist across |
| 6 |
> > > > an emerge ?? |
| 7 |
> > > > |
| 8 |
> > > > I've seen the ebuild.sh which filters out bash read only variables, and |
| 9 |
> > > > I've tried inserting mine into that list, but it doesn't seem to work. |
| 10 |
> > > |
| 11 |
> > > While I think this is mainly a Portage related question, still can you |
| 12 |
> > > explain why you want/need to do this? Or what you want to achieve? |
| 13 |
> > |
| 14 |
> > Because the libc I'm using read's an environment variable to determine |
| 15 |
> > functionality, and the emerge process is removing it and changing the |
| 16 |
> > way libc reacts. |
| 17 |
> |
| 18 |
> Feels like we need to know which environment variable this is and add it |
| 19 |
> to Portage's lists. |
| 20 |
|
| 21 |
It's called UNIXMODE. But where do I add it in Portage's list ?? |
| 22 |
|
| 23 |
Alan. |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-alt@l.g.o mailing list |
Archives