Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ciaran McCreesh <ciaran.mccreesh@...>
Subject: Re: explicit -r0 in ebuild filename
Date: Sun, 30 Mar 2008 03:48:11 +0100
On Sat, 29 Mar 2008 19:39:02 -0700
Brian Harring <ferringb@...> wrote:
> The reason I'm emailing -dev is to ensure there is consensus on 
> leaving off an explicit -r0 in the ebuild name- long term, it seems 
> folks always followed the rule but it needs to be codified due to 
> problems with uniquely identifying the ebuild in the repo.

Uniquely indentifying an ebuild is an issue regardless of whether or
not -r0 is allowed. See PMS section 2.4.

Even ignoring the unique identifiers, banning explicit -r0 globally is
inconsistent anyway. We already allow and use _alpha and _alpha0 (which
mean the same thing) and so on. You'd also be forcing special-casing of
eclasses that would otherwise just use PVR in dep strings.

Please think things through before asking to have pkgcore's bugs 'fixed'
via specification next time...

-- 
Ciaran McCreesh
Attachment:
signature.asc (PGP signature)
Replies:
OT: offensive (Re: explicit -r0 in ebuild filename)
-- Thilo Bangert
Re: explicit -r0 in ebuild filename
-- Mike Frysinger
Re: explicit -r0 in ebuild filename
-- Brian Harring
References:
explicit -r0 in ebuild filename
-- Brian Harring
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
explicit -r0 in ebuild filename
Next by thread:
Re: explicit -r0 in ebuild filename
Previous by date:
explicit -r0 in ebuild filename
Next by date:
Re: explicit -r0 in ebuild filename


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.