public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 09-10-2012
Date: Tue, 25 Sep 2012 11:59:46 +0200	[thread overview]
Message-ID: <20577.32914.7474.976710@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20120925092414.GL37574@gentoo.org>

>>>>> On Tue, 25 Sep 2012, Fabian Groffen wrote:

> In two weeks from now, the council will meet again. This is the time
> to raise and prepare items that the council should put on the agenda
> to discuss or vote on.

> Please respond to this email with agenda items. Please do not
> hestitate to repeat your agenda item here with a pointer if you
> previously suggested one (since the last meeting).

I've two items:

- Allow using EAPI 5 in the tree.
  Portage supports EAPI 5 since version 2.1.11.19.

- Package names:
  Our current spec forbids that package names "end in a hyphen
  followed by one or more digits". This isn't consequent, since it
  still allows PN to be e.g. "foo-1a" which looks like a valid PF.
  OTOH, there's no technical reason for this limitation (backwards
  compatibility issues taken aside).
  Since this issue is open since more than five years, I believe that
  it's time to ask the council for guidance in what direction we
  should go:
    a) Drop the limitation entirely (possibly in a future EAPI).
    b) Make it stricter, i.e. disallow package names ending in a
       hyphen followed by anything that looks like a valid PVR.
       This is current Portage behaviour, and the tree complies with
       it, too.
    c) Leave the spec as it is (and make Portage comply with it).
  See bug 174536 for details.

Ulrich


  reply	other threads:[~2012-09-25 12: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 [this message]
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
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=20577.32914.7474.976710@a1i15.kph.uni-mainz.de \
    --to=ulm@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