1 |
b.n. wrote: |
2 |
|
3 |
> * Overlay eclass overrides eclass from PORTDIR: |
4 |
|
5 |
> Could anyone explain me what does it mean in practice? |
6 |
|
7 |
The cause of this message is that one of the overlays you |
8 |
have configured includes an eclass that already exists in |
9 |
base portage. This happens when the overlay includes |
10 |
ebuilds that require enhanced behavior from a current eclass. |
11 |
|
12 |
The result of this message is that portage is going to run |
13 |
slower than normal unless you do what the error recommends. |
14 |
The short explanation is: |
15 |
|
16 |
When you sync to a portage mirror, you download a set of |
17 |
metadata cache files that were pre-generated and saved on |
18 |
the mirror, that portage can use to build the dependancy |
19 |
list. But the metadata cache is only valid if it has been |
20 |
built using the exact same eclasses as you have locally; |
21 |
changing an eclass could (potentially) alter the dependancy |
22 |
graph. So when portage notices that your metadata is |
23 |
outdated, it will stop using it and get slower. |
24 |
|
25 |
If you run "emerge --regen" every time you sync, portage |
26 |
rebuilds the metadata cache locally, with your copies of the |
27 |
eclass files. This takes a *long* time (it takes 6+ hours |
28 |
on some of my slower machines) but once it has been done, |
29 |
portage will run faster. |
30 |
|
31 |
There's nothing you can do to avoid the problem other than |
32 |
not using the overlay in question. |
33 |
|
34 |
--Mike |