public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] Precedence order of overlays
@ 2007-02-02 13:32 Alan McKinnon
  2007-02-02 14:07 ` Bo Ørsted Andresen
  2007-02-02 14:13 ` [gentoo-user] " Harm Geerts
  0 siblings, 2 replies; 6+ messages in thread
From: Alan McKinnon @ 2007-02-02 13:32 UTC (permalink / raw
  To: gentoo-user

Hi,

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 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.

alan


-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Precedence order of overlays
  2007-02-02 13:32 [gentoo-user] Precedence order of overlays Alan McKinnon
@ 2007-02-02 14:07 ` Bo Ørsted Andresen
  2007-02-02 15:58   ` Alan McKinnon
  2007-02-02 14:13 ` [gentoo-user] " Harm Geerts
  1 sibling, 1 reply; 6+ messages in thread
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	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: Precedence order of overlays
  2007-02-02 13:32 [gentoo-user] Precedence order of overlays Alan McKinnon
  2007-02-02 14:07 ` Bo Ørsted Andresen
@ 2007-02-02 14:13 ` Harm Geerts
  2007-02-02 16:01   ` Alan McKinnon
  1 sibling, 1 reply; 6+ messages in thread
From: Harm Geerts @ 2007-02-02 14:13 UTC (permalink / raw
  To: gentoo-user

On Friday 02 February 2007, Alan McKinnon wrote:
> Hi,
>
> 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 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.

This is controlled by the order in which they apear in PORTDIR_OVERLAY.
The last overlay that matches a package takes precedence.
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Precedence order of overlays
  2007-02-02 14:07 ` Bo Ørsted Andresen
@ 2007-02-02 15:58   ` Alan McKinnon
  2007-02-02 17:39     ` Bo Ørsted Andresen
  0 siblings, 1 reply; 6+ messages in thread
From: Alan McKinnon @ 2007-02-02 15:58 UTC (permalink / raw
  To: gentoo-user

On Friday 02 February 2007, Bo Ørsted Andresen wrote:
> > 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.

Excellent, this is exactly what I needed to know. Thanks.

> > 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.

Why is that? Because 20050101 is a bigger number than 9999? If so, it's 
not a problem, as the ebuilds don't use version numbers formatted that 
way

alan


-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: Precedence order of overlays
  2007-02-02 14:13 ` [gentoo-user] " Harm Geerts
@ 2007-02-02 16:01   ` Alan McKinnon
  0 siblings, 0 replies; 6+ messages in thread
From: Alan McKinnon @ 2007-02-02 16:01 UTC (permalink / raw
  To: gentoo-user

On Friday 02 February 2007, Harm Geerts wrote:
> On Friday 02 February 2007, Alan McKinnon wrote:

> > 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 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.
>
> This is controlled by the order in which they apear in
> PORTDIR_OVERLAY. The last overlay that matches a package takes
> precedence.

Thanks for this, but Bo beat you to the correct answer by 6 minutes :-)

I think I'll make a suggestion to the appropriate maintainer to have 
this documented in man 5 make.conf

alan



-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Precedence order of overlays
  2007-02-02 15:58   ` Alan McKinnon
@ 2007-02-02 17:39     ` Bo Ørsted Andresen
  0 siblings, 0 replies; 6+ messages in thread
From: Bo Ørsted Andresen @ 2007-02-02 17:39 UTC (permalink / raw
  To: gentoo-user

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

On Friday 02 February 2007 16:58:47 Alan McKinnon wrote:
> > Do note that portage will consider e.g. foo-20050101.ebuild a higher
> > version than foo-9999.ebuild.
>
> Why is that? Because 20050101 is a bigger number than 9999?

Yes.

-- 
Bo Andresen

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-02-02 17:45 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-02 13:32 [gentoo-user] Precedence order of overlays Alan McKinnon
2007-02-02 14:07 ` Bo Ørsted Andresen
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

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