Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT

[Joakim Tjernlund]

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

Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
repo has newer versions?

 Jocke