1 |
On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote: |
2 |
> On 05/07/2015 11:43 PM, Joakim Tjernlund wrote: |
3 |
> > On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote: |
4 |
> > > On 05/07/2015 03:51 AM, Joakim Tjernlund wrote: |
5 |
> > > > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote: |
6 |
> > > > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote: |
7 |
> > > > > > On 05/06/15 14:57, Joakim Tjernlund wrote: |
8 |
> > > > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote: |
9 |
> > > > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote: |
10 |
> > > > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote: |
11 |
> > > > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote: |
12 |
> > > > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote: |
13 |
> > > > > > > > > > > > On 05/06/15 12:41, Joakim Tjernlund wrote: |
14 |
> > > > > > > > > > > > > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote: |
15 |
> > > > > > > > > > > > > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: |
16 |
> > > > > > > > > > > > > > > On 05/06/15 09:54, Joakim Tjernlund wrote: |
17 |
> > > > > > > > > > > > > > > > I am trying to rebuild an old cross sysroot and I got problems. |
18 |
> > > > > > > > > > > > > > > > I cannot make emerge to select my old ebuilds in an overlay over those |
19 |
> > > > > > > > > > > > > > > > in /usr/portage. |
20 |
> > > > > > > > > > > > > > > > |
21 |
> > > > > > > > > > > > > > > > What new is since last time I did this is /etc/portage/repos.conf/ |
22 |
> > > > > > > > > > > > > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter |
23 |
> > > > > > > > > > > > > > > > what I set PORTAGE_CONFIGROOT / ROOT to ? |
24 |
> > > > > > > > > > > > > > > > |
25 |
> > > > > > > > > > > > > > > > Jocke |
26 |
> > > > > > > > > > > > > > > > |
27 |
> > > > > > > > > > > > > > > |
28 |
> > > > > > > > > > > > > > > It instantiates 2 config instances, one using /etc/portage/repos.conf |
29 |
> > > > > > > > > > > > > > > (for build time DEPEND) and another one using |
30 |
> > > > > > > > > > > > > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND). |
31 |
> > > > > > > > > > > > > > > You can see that it's joined with PORTAGE_CONFIGROOT in the |
32 |
> > > > > > > > > > > > > > > load_repository_config function: |
33 |
> > > > > > > > > > > > > > > |
34 |
> > > > > > > > > > > > > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py |
35 |
> > > > > > > > > > > > > > > ?id= |
36 |
> > > > > > > > > > > > > > > 0f19 |
37 |
> > > > > > > > > > > > > > > 11 |
38 |
> > > > > > > > > > > > > > > 13cc |
39 |
> > > > > > > > > > > > > > > cd04 |
40 |
> > > > > > > > > > > > > > > 9e11 |
41 |
> > > > > > > > > > > > > > > fdbe |
42 |
> > > > > > > > > > > > > > > 73 |
43 |
> > > > > > > > > > > > > > > 493eb1efbf4bf89e#n971 |
44 |
> > > > > > > > > > > > > > |
45 |
> > > > > > > > > > > > > > I see, doesn't this prevent exactly what I want to do? |
46 |
> > > > > > > > > > > > > > |
47 |
> > > > > > > > > > > > > > I can't see why this should be needed, it only creates a mess, another example: |
48 |
> > > > > > > > > > > > > > I tried to specify exact version of my old binutils and while that worked, |
49 |
> > > > > > > > > > > > > > portage |
50 |
> > > > > > > > > > > > > > wanted |
51 |
> > > > > > > > > > > > > > to pull in a newer binutils-config from the hosts master gentoo repo and |
52 |
> > > > > > > > > > > > > > thus the build failed. |
53 |
> > > > > > > > > > > > > > |
54 |
> > > > > > > > > > > > > > If a someone really wants this behaviour, he can just add the hosts master repo |
55 |
> > > > > > > > > > > > > > in his PORTAGE_CONFIGROOT IMHO |
56 |
> > > > > > > > > > > > > > |
57 |
> > > > > > > > > > > > |
58 |
> > > > > > > > > > > > Maybe emerge --root-deps=rdeps is what you are looking for. This will |
59 |
> > > > > > > > > > > > cause it to ignore DEPEND. |
60 |
> > > > > > > > > > > |
61 |
> > > > > > > > > > > That is not the same is it? if I "emerge ncurses" it will build ncurses but still |
62 |
> > > > > > > > > > > take the ebuild from the hosts master since it is newer version. |
63 |
> > > > > > > > > > > |
64 |
> > > > > > > > > > > I realize now that I can change what repos are searched by using |
65 |
> > > > > > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf/ |
66 |
> > > > > > > > > > > but I still find the default behaviour very confusing and I don't see that it is useful. |
67 |
> > > > > > > > > > |
68 |
> > > > > > > > > > The idea is that you have separate repositories configured for each |
69 |
> > > > > > > > > > ROOT. If it's satisfying a build-time DEPEND that will be installed into |
70 |
> > > > > > > > > > ROOT=/, then it's supposed to use the repositories configured for ROOT=/. |
71 |
> > > > > > > > > |
72 |
> > > > > > > > > I see, but in my case I only install into my sysroot so I don't want this behaviour. |
73 |
> > > > > > > > |
74 |
> > > > > > > > So, why don't you use the --root-deps option? |
75 |
> > > > > > > |
76 |
> > > > > > > Just did(and --root-deps=rdeps too) and it didn't work, still wants to use |
77 |
> > > > > > > my newer hosts pkgs. :( |
78 |
> > > > > > |
79 |
> > > > > > It shouldn't do that. It sounds like maybe the [gentoo] config |
80 |
> > > > > > from/usr/share/portage/config/repos.conf is the source of your problems, |
81 |
> > > > > > since you $PORTAGE_CONFIGROOT config will always inherit that. Would |
82 |
> > > > > > that be consistent with your observations? |
83 |
> > > > > |
84 |
> > > > > Moving that file out of the way changed things, now I got I profile error: |
85 |
> > > > > !!! Unable to parse profile: '/etc/portage/make.profile' |
86 |
> > > > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not found: |
87 |
> > > > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent' |
88 |
> > > > > !!! Your current profile is invalid. If you have just changed your profile |
89 |
> > > > > !!! configuration, you should revert back to the previous configuration. |
90 |
> > > > > !!! Allowed actions are limited to --help, --info, --search, --sync, and |
91 |
> > > > > !!! --version. |
92 |
> > > > > |
93 |
> > > > > Which I think is a problem in my cross env. |
94 |
> > > > |
95 |
> > > > No, this is not it. Portage just bails when reading the host profile which it should not. |
96 |
> > > > |
97 |
> > > > Note: defining |
98 |
> > > > PORTAGE_REPOSITORIES=/my/own/repos.conf |
99 |
> > > > gives the same error. |
100 |
> > > > |
101 |
> > > |
102 |
> > > According to the error message, your transmode profile inherits a gentoo |
103 |
> > > profile, so you need the gentoo repository (at least the relevant profile). |
104 |
> > |
105 |
> > I have a my own profile in PORTAGE_CONFIGROOT which does not |
106 |
> > reference the host /etc/portage/make.profile at all so I think |
107 |
> > portage is using the wrong profile. |
108 |
> |
109 |
> When using ROOT=/foo, it always instantiates 2 profiles, and it uses one |
110 |
> profile for ROOT=/foo and the other profile for ROOT=/. |
111 |
|
112 |
This makes sense when just using ROOT, not when cross compiling. |
113 |
If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes |
114 |
sense to add the hosts profile as it has little to nothing to |
115 |
do with my cross target. |
116 |
How would a cross target use the hosts profile sensibly? |
117 |
|
118 |
> |
119 |
> > Futhermore, it does not understand the host profile, probably |
120 |
> > because my own PORTAGE_CONFIGROOT don't have profile-formats = portage-2 |
121 |
> |
122 |
> You're saying this beciase of the above ParseError? I think maybe what |
123 |
> you want to do keep the default /usr/share/portage/config/repos.conf and |
124 |
> mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask. |
125 |
|
126 |
That is what I am doing now, but that still includes the hosts profile I think ? |
127 |
|
128 |
Jocke |