Gentoo Archives: gentoo-portage-dev

From: Joakim Tjernlund <joakim.tjernlund@×××××××××.se>
To: "gentoo-portage-dev@l.g.o" <gentoo-portage-dev@l.g.o>
Subject: Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT
Date: Wed, 06 May 2015 22:09:11
Message-Id: 1430950145.27859.154.camel@transmode.se
In Reply to: Re: [gentoo-portage-dev] repos.conf location w.r.t PORTAGE_CONFIGROOT by Joakim Tjernlund
1 On Wed, 2015-05-06 at 21:57 +0000, Joakim Tjernlund wrote:
2 > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote:
3 > > On 05/06/15 14:30, Joakim Tjernlund wrote:
4 > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote:
5 > > > > On 05/06/15 13:22, Joakim Tjernlund wrote:
6 > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote:
7 > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote:
8 > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote:
9 > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote:
10 > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote:
11 > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems.
12 > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those
13 > > > > > > > > > > in /usr/portage.
14 > > > > > > > > > >
15 > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/
16 > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter
17 > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ?
18 > > > > > > > > > >
19 > > > > > > > > > > Jocke
20 > > > > > > > > > >
21 > > > > > > > > >
22 > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf
23 > > > > > > > > > (for build time DEPEND) and another one using
24 > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND).
25 > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the
26 > > > > > > > > > load_repository_config function:
27 > > > > > > > > >
28 > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113
29 > > > > > > > > > cc
30 > > > > > > > > > cd04
31 > > > > > > > > > 9e11
32 > > > > > > > > > fdbe
33 > > > > > > > > > 73
34 > > > > > > > > > 493eb1efbf4bf89e#n971
35 > > > > > > > >
36 > > > > > > > > I see, doesn't this prevent exactly what I want to do?
37 > > > > > > > >
38 > > > > > > > > I can't see why this should be needed, it only creates a mess, another example:
39 > > > > > > > > I tried to specify exact version of my old binutils and while that worked, portage wanted
40 > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and
41 > > > > > > > > thus the build failed.
42 > > > > > > > >
43 > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo
44 > > > > > > > > in his PORTAGE_CONFIGROOT IMHO
45 > > > > > > > >
46 > > > > > >
47 > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will
48 > > > > > > cause it to ignore DEPEND.
49 > > > > >
50 > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still
51 > > > > > take the ebuild from the hosts master since it is newer version.
52 > > > > >
53 > > > > > I realize now that I can change what repos are searched by using
54 > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/
55 > > > > > but I still find the default behaviour very confusing and I don't see that it is useful.
56 > > > >
57 > > > > The idea is that you have separate repositories configured for each
58 > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into
59 > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/.
60 > > >
61 > > > I see, but in my case I only install into my sysroot so I don't want this behaviour.
62 > >
63 > > So, why don't you use the --root-deps option?
64 >
65 > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use
66 > my newer hosts pkgs. :(
67 >
68 > >
69 > > > Can you not add a test for CHOST/CBULID/CTARGET (never remeber which is which) so portage
70 > > > only adds the hosts repo if they are the same?
71 > > > Basically only add the master repo if not cross-building?
72 > >
73 > > It would have to be tied to an option like --root-deps. I still suspect
74 > > that --root-deps is what you really want.
75 >
76 > No, I really think that portage is over doing things here.
77 > Anyone that is using ROOT and PORTAGE_CONFIGROOT only needs the main repo iff
78 >
79
80 hmm, is ROOT and PORTAGE_CONFIGROOT really useful for non cross builds? Installing DEPEND
81 into host require you use the same conf as the host(USE mainly I guess)?
82
83 Jocke

Replies