[SOLVED] Portage search prio.: overlay vs. /usr/portage/

[the_bat]

Hi,

I'm maintaining some locally modifed ebuilds in /usr/local/portage. Whenever an update to a package ships I re-apply my patches and update stuff in /usr/local/portage.

Now I'm having two versions of, e.g., xorg-server-1.1.1-r5.ebuild in my system, one in /usr/portage/... and the other in /usr/local/portage... .

How does portage decide which one to emerge when I call

Code: Select all

emerge -u xorg-server

? It seems that /usr/portage always takes precedence. Is this specified or adjustable somewhere?

I can explicitely call emerge with the full path to the ebuild as parameter, however, I want the right thing to happen on

Code: Select all

emerge -uDN world

.

Up to now I increase the release version by one in my overlay directory, thereby forcing portage to take the higher version. But this way, I don't see updates in the main tree, until one version later. Is there any other way to handle this issue? I tried the append another minor version number to the ebuild (e.g., -r8.1) but portage does not handle this.

Any hints are appreciated.

Cheers,
Martin

[Genone]

PORTDIR_OVERLAY has a higher priority than PORTDIR (as the name implies).

[the_bat]

Thanks for the answer.

In fact, my tests were some month old. It seems to work now as expected.

Sorry for the confusion, my mistake.