| 1 |
On Tuesday 23 August 2005 06:40, Brian Harring wrote: |
| 2 |
> On Mon, Aug 22, 2005 at 11:33:23PM +0200, Marius Mauch wrote: |
| 3 |
> > Theoretical discussions about this are pointless IMO without |
| 4 |
> > numbers/facts to back things up. |
| 5 |
> |
| 6 |
> I'd posit theroetical discussions about this are pointless without |
| 7 |
> getting ebuild dev's to give a yay/nay on whether they want it or not; |
| 8 |
> not much for trying to force it down their throats if they don't want |
| 9 |
> it (more work, essentially). |
| 10 |
|
| 11 |
I don't really see what it has to do with ebuild devs... We're talking about |
| 12 |
the user's environment leaking into the portage build environment, no? |
| 13 |
Environment vars used by ebuilds can/should be set by users in a portage |
| 14 |
configuration file rather than being added to the environment. The only |
| 15 |
issue i see here is user customizations - fex, a hypothetical colorgcc that |
| 16 |
gets its config info from the env. |
| 17 |
|
| 18 |
-- |
| 19 |
Jason Stubbs |
Archives