| 1 |
On Thu, 2008-12-11 at 11:21 +0100, Michael Haubenwallner wrote: |
| 2 |
> On Thu, 2008-12-11 at 09:30 +0000, Alan Hourihane wrote: |
| 3 |
> |
| 4 |
> > > But portage does set it as part of the ebuild-environment, so the |
| 5 |
> > > ebuilds can encode into the built package for which EPREFIX it is built. |
| 6 |
> > |
| 7 |
> > Where does portage set it ? |
| 8 |
> |
| 9 |
> Somewhere inside python, before starting bash to interpret the ebuilds. |
| 10 |
> |
| 11 |
> What are you after? |
| 12 |
|
| 13 |
EPREFIX isn't set by portage here, and only in the environment. So I'm |
| 14 |
trying to find out what's wrong with portage and/or python. |
| 15 |
|
| 16 |
Alan. |
Archives