| 1 |
On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: |
| 2 |
> On 05/06/15 09:54, Joakim Tjernlund wrote: |
| 3 |
> > I am trying to rebuild an old cross sysroot and I got problems. |
| 4 |
> > I cannot make emerge to select my old ebuilds in an overlay over those |
| 5 |
> > in /usr/portage. |
| 6 |
> > |
| 7 |
> > What new is since last time I did this is /etc/portage/repos.conf/ |
| 8 |
> > I suspect emerge always reads /etc/portage/repos.conf/ no matter |
| 9 |
> > what I set PORTAGE_CONFIGROOT / ROOT to ? |
| 10 |
> > |
| 11 |
> > Jocke |
| 12 |
> > |
| 13 |
> |
| 14 |
> It instantiates 2 config instances, one using /etc/portage/repos.conf |
| 15 |
> (for build time DEPEND) and another one using |
| 16 |
> $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND). |
| 17 |
> You can see that it's joined with PORTAGE_CONFIGROOT in the |
| 18 |
> load_repository_config function: |
| 19 |
> |
| 20 |
> https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11fdbe73 |
| 21 |
> 493eb1efbf4bf89e#n971 |
| 22 |
|
| 23 |
I see, doesn't this prevent exactly what I want to do? |
| 24 |
|
| 25 |
I can't see why this should be needed, it only creates a mess, another example: |
| 26 |
I tried to specify exact version of my old binutils and while that worked, portage wanted |
| 27 |
to pull in a newer binutils-config from the hosts master gentoo repo and |
| 28 |
thus the build failed. |
| 29 |
|
| 30 |
If a someone really wants this behaviour, he can just add the hosts master repo |
| 31 |
in his PORTAGE_CONFIGROOT IMHO |
| 32 |
|
| 33 |
Jocke |
Archives