| 1 |
On Thu, 2008-12-11 at 12:35 +0100, Fabian Groffen wrote: |
| 2 |
> On 11-12-2008 11:13:35 +0000, Alan Hourihane wrote: |
| 3 |
> > On Thu, 2008-12-11 at 11:21 +0100, Michael Haubenwallner wrote: |
| 4 |
> > > On Thu, 2008-12-11 at 09:30 +0000, Alan Hourihane wrote: |
| 5 |
> > > |
| 6 |
> > > > > But portage does set it as part of the ebuild-environment, so the |
| 7 |
> > > > > ebuilds can encode into the built package for which EPREFIX it is built. |
| 8 |
> > > > |
| 9 |
> > > > Where does portage set it ? |
| 10 |
> > > |
| 11 |
> > > Somewhere inside python, before starting bash to interpret the ebuilds. |
| 12 |
> > > |
| 13 |
> > > What are you after? |
| 14 |
> > |
| 15 |
> > EPREFIX isn't set by portage here, and only in the environment. So I'm |
| 16 |
> > trying to find out what's wrong with portage and/or python. |
| 17 |
> |
| 18 |
> look in var/lib/portage/pym/portage/const_autotool.py, there it is |
| 19 |
> hardcoded and set for the Python side. That's the base for the bash |
| 20 |
> side. |
| 21 |
|
| 22 |
Yep, thanks to haubi too on irc. He's pointed me at the same location. |
| 23 |
|
| 24 |
Alan. |
Archives