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

[Joakim Tjernlund]

On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
> On 05/06/15 12:41, Joakim Tjernlund wrote:
> > 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=0f191113cccd049e11
> > > > fdbe
> > > > 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
> > >
>
> Maybe emerge --root-deps=rdeps is what you are looking for. This will
> cause it to ignore DEPEND.

That is not the same is it? if I "emerge ncurses" it will build ncurses but still
take the ebuild from the hosts master since it is newer version.

I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/
but I still find the default behaviour very confusing and I don't see that it is useful.

What is 'extra_files' in load_repository_config()? Can I as a user add those or does portage
add some of its own?
>
> >
> > Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master
> > repo has newer versions?
> >
> >  Jocke
> >
>
> You can use repo atoms in /etc/portage/package.mask. For example,
> 'sys-devel/binutils-config::gentoo', or '*/*::gentoo'.

Nice! Can I also mask everything '*/*::gentoo' and then only unmask sys-devel/binutils-config::gentoo ?

 Jocke