From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Precedence order of overlays
Date: Fri, 2 Feb 2007 15:07:46 +0100 [thread overview]
Message-ID: <200702021507.51044.bo.andresen@zlin.dk> (raw)
In-Reply-To: <200702021532.39245.alan@linuxholdings.co.za>
[-- 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 --]
next prev parent reply other threads:[~2007-02-02 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 13:32 [gentoo-user] Precedence order of overlays Alan McKinnon
2007-02-02 14:07 ` Bo Ørsted Andresen [this message]
2007-02-02 15:58 ` Alan McKinnon
2007-02-02 17:39 ` Bo Ørsted Andresen
2007-02-02 14:13 ` [gentoo-user] " Harm Geerts
2007-02-02 16:01 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200702021507.51044.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox