public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-user] Precedence order of overlays
  @ 2007-02-02 14:07 99% ` Bo Ørsted Andresen
  0 siblings, 0 replies; 1+ results
From: Bo Ørsted Andresen @ 2007-02-02 14:07 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2007-02-02 13:32     [gentoo-user] Precedence order of overlays Alan McKinnon
2007-02-02 14:07 99% ` Bo Ørsted Andresen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox