public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 09-10-2012
Date: Tue, 2 Oct 2012 23:56:49 -0700	[thread overview]
Message-ID: <CAEdQ38HmZ_M-DuR+n_pri3YxoRvmKom0naBUEY451s+i3LdGcg@mail.gmail.com> (raw)
In-Reply-To: <20587.57038.690414.911541@a1i15.kph.uni-mainz.de>

On Tue, Oct 2, 2012 at 11:44 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Wed, 3 Oct 2012, Donnie Berkholz wrote:
>
>> On 15:13 Thu 27 Sep     , Brian Harring wrote:
>>> What for?  So someone can name their package foo-1?  Is that really
>>> such a major gap we're willing to induce breakage?
>>>
>>> Will anyone even !@#*ing use a package names foo-1?  I've yet to see
>>> an example given, just ignoring of the breakage it will induce.
>
>> I tend to agree. What value does this provide? It creates additional
>> work for no proven real-world benefit.
>
> As I said before, the point is that the PMS isn't consequent, and
> that there is a discrepancy between Portage and the PMS. Portage
> is stricter because it also forbids package names like foo-1a or
> foo-1_alpha that could be confused with a package name followed by
> a version.
>
> (Something along the lines of "a hyphen followed by a digit must not
> occur anywhere in a package name" would be even simpler. We cannot
> do that because there are packages like font-adobe-100dpi that don't
> conform with it.)
>
> Ulrich
>

This doesn't seem that difficult. How about "$PN must not end in a
hyphen followed by 1 or more digits"?


  reply	other threads:[~2012-10-03  9:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  9:24 [gentoo-project] Call for agenda items -- Council meeting 09-10-2012 Fabian Groffen
2012-09-25  9:59 ` Ulrich Mueller
2012-09-27  6:19   ` Ulrich Mueller
2012-09-27 22:13     ` Brian Harring
2012-09-28  0:14       ` Ulrich Mueller
2012-09-28 12:12         ` Brian Harring
2012-10-03  5:04       ` Donnie Berkholz
2012-10-03  6:44         ` Ulrich Mueller
2012-10-03  6:56           ` Matt Turner [this message]
2012-10-03  8:31             ` Ulrich Mueller
2012-09-29 15:51     ` Ciaran McCreesh
2012-09-29 16:04       ` Ulrich Mueller
2012-09-29 16:10         ` Ciaran McCreesh
2012-09-25 19:32 ` Pacho Ramos
2012-10-02 11:30   ` Fabian Groffen
2012-10-03 17:18     ` Pacho Ramos
2012-10-04 18:32       ` Pacho Ramos
2012-10-05  6:28         ` Fabian Groffen
2012-10-05  6:41           ` Pacho Ramos
2012-10-05  6:43           ` Patrick Lauer
2012-10-05  8:46             ` Ulrich Mueller
2012-10-05 10:31               ` Rich Freeman
2012-10-05 14:51                 ` Jeff Horelick
2012-10-05 17:35                 ` Pacho Ramos

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=CAEdQ38HmZ_M-DuR+n_pri3YxoRvmKom0naBUEY451s+i3LdGcg@mail.gmail.com \
    --to=mattst88@gentoo.org \
    --cc=gentoo-project@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