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 04:20:57 +0100	[thread overview]
Message-ID: <20080330042057.089d0f8e@snowcone> (raw)
In-Reply-To: <20080330031237.GA8925@seldon.hsd1.ca.comcast.net>

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

On Sat, 29 Mar 2008 20:12:37 -0700
Brian Harring <ferringb@gmail.com> wrote:
> What this email is about is the inconsistancy allowed on disk and the 
> fact explicitly leaving -r0 out of on disk name thus far seems to be 
> an unofficial gentoo-x86 standard.

Which means it's not something to be specified in PMS. Devmanual,
possibly, but that's a whole different kettle of fish. (We don't
specify that you should use tabs for indenting in ebuilds in PMS
either.)

> > Uniquely indentifying an ebuild is an issue regardless of whether or
> > not -r0 is allowed. See PMS section 2.4.
> 
> Stating that each cpv in a repo must be unique ignores that there are 
> multiple ways to specify certain cpv's due to implicit 0 (both suffix 
> and rev).  Frankly it's pretty stupid to state "it must be unique" 
> while allowing multiple ways for people to screw up and violate that 
> constraint.
> 
> Intentionally allowing gotchas is dumb behaviour- removal of the 
> gotcha is the intention here.

PMS is going with the tree here. There have always been equivalent but
not equal ways of specifying versions, and people use them. You don't
want to start breaking people who use >=..._alpha0 when the version in
the tree uses plain _alpha, for example. Package managers have to deal
with this kind of thing, and it's not one of those areas where we can
change reality with little or no impact.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2008-03-30  3:21 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
2008-03-30  3:12   ` Brian Harring
2008-03-30  3:20     ` Ciaran McCreesh [this message]
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=20080330042057.089d0f8e@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