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