1 |
On Wed, 2015-05-06 at 12:54 -0700, Zac Medico wrote: |
2 |
> On 05/06/15 12:41, Joakim Tjernlund wrote: |
3 |
> > On Wed, 2015-05-06 at 19:13 +0000, Joakim Tjernlund wrote: |
4 |
> > > On Wed, 2015-05-06 at 11:37 -0700, Zac Medico wrote: |
5 |
> > > > On 05/06/15 09:54, Joakim Tjernlund wrote: |
6 |
> > > > > I am trying to rebuild an old cross sysroot and I got problems. |
7 |
> > > > > I cannot make emerge to select my old ebuilds in an overlay over those |
8 |
> > > > > in /usr/portage. |
9 |
> > > > > |
10 |
> > > > > What new is since last time I did this is /etc/portage/repos.conf/ |
11 |
> > > > > I suspect emerge always reads /etc/portage/repos.conf/ no matter |
12 |
> > > > > what I set PORTAGE_CONFIGROOT / ROOT to ? |
13 |
> > > > > |
14 |
> > > > > Jocke |
15 |
> > > > > |
16 |
> > > > |
17 |
> > > > It instantiates 2 config instances, one using /etc/portage/repos.conf |
18 |
> > > > (for build time DEPEND) and another one using |
19 |
> > > > $PORTAGE_CONFIGROOT/etc/portage/repos.conf (for run time {P,R}DEPEND). |
20 |
> > > > You can see that it's joined with PORTAGE_CONFIGROOT in the |
21 |
> > > > load_repository_config function: |
22 |
> > > > |
23 |
> > > > https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/repository/config.py?id=0f191113cccd049e11 |
24 |
> > > > fdbe |
25 |
> > > > 73 |
26 |
> > > > 493eb1efbf4bf89e#n971 |
27 |
> > > |
28 |
> > > I see, doesn't this prevent exactly what I want to do? |
29 |
> > > |
30 |
> > > I can't see why this should be needed, it only creates a mess, another example: |
31 |
> > > I tried to specify exact version of my old binutils and while that worked, portage wanted |
32 |
> > > to pull in a newer binutils-config from the hosts master gentoo repo and |
33 |
> > > thus the build failed. |
34 |
> > > |
35 |
> > > If a someone really wants this behaviour, he can just add the hosts master repo |
36 |
> > > in his PORTAGE_CONFIGROOT IMHO |
37 |
> > > |
38 |
> |
39 |
> Maybe emerge --root-deps=rdeps is what you are looking for. This will |
40 |
> cause it to ignore DEPEND. |
41 |
|
42 |
That is not the same is it? if I "emerge ncurses" it will build ncurses but still |
43 |
take the ebuild from the hosts master since it is newer version. |
44 |
|
45 |
I realize now that I can change what repos are searched by using PORTAGE_REPOSITORIES=/my/own/repos.conf/ |
46 |
but I still find the default behaviour very confusing and I don't see that it is useful. |
47 |
|
48 |
What is 'extra_files' in load_repository_config()? Can I as a user add those or does portage |
49 |
add some of its own? |
50 |
> |
51 |
> > |
52 |
> > Is there a way to make portage to prefer ebuilds from an overlay/other repo even if the master |
53 |
> > repo has newer versions? |
54 |
> > |
55 |
> > Jocke |
56 |
> > |
57 |
> |
58 |
> You can use repo atoms in /etc/portage/package.mask. For example, |
59 |
> 'sys-devel/binutils-config::gentoo', or '*/*::gentoo'. |
60 |
|
61 |
Nice! Can I also mask everything '*/*::gentoo' and then only unmask sys-devel/binutils-config::gentoo ? |
62 |
|
63 |
Jocke |