public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] explicit -r0 in ebuild filename
Date: Sun, 30 Mar 2008 03:48:11 +0100	[thread overview]
Message-ID: <20080330034811.39942523@snowcone> (raw)
In-Reply-To: <20080330023902.GA8787@seldon.hsd1.ca.comcast.net>

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

On Sat, 29 Mar 2008 19:39:02 -0700
Brian Harring <ferringb@gmail.com> 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-30  2:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30  2:39 [gentoo-dev] explicit -r0 in ebuild filename Brian Harring
2008-03-30  2:48 ` Ciaran McCreesh [this message]
2008-03-30  3:12   ` Brian Harring
2008-03-30  3:20     ` Ciaran McCreesh
2008-03-30  4:16       ` Brian Harring
2008-03-30  4:40         ` Ciaran McCreesh
2008-03-30  9:39           ` Brian Harring
2008-03-30 13:10             ` [gentoo-dev] " Duncan
2008-03-30 14:54               ` Marijn Schouten (hkBst)
2008-03-30 15:38                 ` Ioannis Aslanidis
2008-03-30 17:56                   ` Richard Freeman
2008-03-30 18:26             ` [gentoo-dev] " Ciaran McCreesh
2008-03-30 16:24   ` Mike Frysinger
2008-03-30 18:18     ` Ciaran McCreesh
2008-03-30 18:59       ` Mike Frysinger
2008-03-30 23:40         ` Brian Harring
2008-03-30 23:46           ` Ciaran McCreesh
2008-03-31  0:02             ` Brian Harring
2008-03-31  0:06               ` Ciaran McCreesh
2008-03-31  0:29                 ` Brian Harring
2008-04-01 10:44                   ` Ciaran McCreesh
2008-04-04  6:39                   ` Bo Ørsted Andresen
2008-03-31  7:40   ` OT: offensive (Re: [gentoo-dev] explicit -r0 in ebuild filename) Thilo Bangert
2008-03-31  7:49     ` Anders Ossowicki
2008-03-31  8:29       ` Patrick Lauer
2008-03-31  8:48         ` Anders Ossowicki
2008-03-31 16:07     ` Jeroen Roovers
2008-03-30  3:36 ` [gentoo-dev] Re: explicit -r0 in ebuild filename Michael Sterrett -Mr. Bones.-
2008-03-30  3:41   ` Ciaran McCreesh

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=20080330034811.39942523@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-dev@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