> I have several packages that I maintain my own ebuilds for, as it's CVS > sources. I keep these in /usr/local/portage. As it happens ebuilds for > these same packages are also in layman, and I have the relevant overlay > enabled. > > So far it would appear that my local overlay is taking precedence over > layman. I've read the layman docs and there is an option for > precedence, but it seems to apply to layman only, and that's not what I > want. The portage docs seems to be sparse on this matter of overlays. > > I want to guarantee that foo-9999.ebuild in /usr/local/portage will be > emerged in preference to an identically named and versioned ebuild in > layman. How do I do that?
If several overlays contain the same version of an ebuild portage will only see the one from the overlay that is listed last in PORTDIR_OVERLAY. This is why /usr/portage/local/layman/make.conf prepends layman overlays to PORTDIR_OVERLAY rather than appending them. > If I can't guarantee this, I'd also be happy bumping my ebuilds to > foo-99999.ebuild, but I'd rather do it with a config option if > possible. Do note that portage will consider e.g. foo-20050101.ebuild a higher version than foo-9999.ebuild. -- Bo Andresen
pgpVPXr3UmMtl.pgp
Description: PGP signature
