From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] ekeyword and ordering
Date: Mon, 6 Jun 2005 18:26:23 -0400 [thread overview]
Message-ID: <20050606222623.GI9084@kaf.zko.hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Hi guys,
As some of you have noticed, I made a change recently in ekeyword that
causes ekeyword to alphabetize the keywords. I've realized I should
have brought it up for discussion before making the change to the
program. On that note, I apologize for unilaterally making that
change without consulting the developer body for opinions.
Here is the the fuzzy history of keywording in a nutshell. Please
bear in mind that these bullet points happened over a period of years.
- Daniel originally wanted them alphabetized.
- A few people, myself included, pointed out that there's some
valuable information available when keywords are always added to
the end rather than being alphabetized. In particular, the
concept of a "maintainer arch" is possible, in which the first
arch in the list is supposed to indicate general stability of
the ebuild, a leader for other arches to follow.
- Some people disagreed with the "maintainer arch" concept. They
felt that the arch teams do a better job of testing than some
maintainers, and there's no point waiting for a maintainer to
decide something is stable.
- Some developers recently mentioned to me that alphabetizing
would probably be fine. At this point I felt that the tree was
diluted enough that there was no point resisting, so I went
ahead and made the change silently.
- My action was questioned privately on IRC, and I realized
I made the decision without proper discussion. So I'm writing
this email.
Honestly, the arguments aren't very strong in either direction.
I think everybody understands this, but nonetheless people have their
preferences. Here are some of the basic arguments:
alpha
-----------------------------
- looks nicer (subjective)
- easier to tell at a glance if a given keyword is in the list
append
-----------------------------
- slightly less cvs/rsync traffic
- allows "maintainer arch" to continue until another solution is
produced, for those who still depend on that method
- some developers are accustomed to the "append" method and don't want
things to change, at least not without discussion
I am willing to revert the ekeyword change if that is what devs would
prefer, but I won't make the change without a discussion on -dev,
which was my mistake last time. Your thoughts?
If the thread isn't obviously unified one direction or the other,
I guess we'll eventually put this up to a developer or manager vote
(I'm not sure which is appropriate)
Regards,
Aron
--
Aron Griffis
Gentoo Linux Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-06-06 22:26 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:26 Aron Griffis [this message]
2005-06-06 22:41 ` [gentoo-dev] ekeyword and ordering Mike Frysinger
2005-06-06 22:49 ` Stephen P. Becker
2005-06-07 12:16 ` Luca Barbato
2005-06-07 20:58 ` Danny van Dyk
2005-06-09 13:19 ` foser
2005-06-09 13:37 ` Lars Weiler
2005-06-09 15:59 ` [gentoo-dev] " Duncan
2005-06-09 15:29 ` [gentoo-dev] " Danny van Dyk
2005-06-09 15:50 ` Stephen P. Becker
2005-06-10 14:55 ` foser
2005-06-10 16:33 ` Mike Frysinger
2005-06-11 8:15 ` foser
2005-06-11 8:28 ` Jason Stubbs
2005-06-11 8:48 ` foser
2005-06-11 15:21 ` Joshua Baergen
2005-06-11 16:31 ` Diego 'Flameeyes' Pettenò
2005-06-11 18:00 ` Joshua Baergen
2005-06-11 9:06 ` Bryan Oestergaard
2005-06-11 18:46 ` Aron Griffis
2005-08-01 17:06 ` foser
2005-08-01 17:43 ` Aron Griffis
2005-06-11 20:37 ` Mike Frysinger
2005-06-10 17:19 ` Aron Griffis
2005-06-11 0:04 ` Georgi Georgiev
2005-06-11 12:48 ` Aron Griffis
2005-06-12 0:39 ` Georgi Georgiev
2005-06-12 2:18 ` Aron Griffis
2005-06-06 22:43 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2005-06-09 13:06 ` foser
2005-06-06 22:47 ` [gentoo-dev] " Lars Weiler
2005-06-07 3:19 ` Aaron Walker
2005-06-07 18:35 ` Donnie Berkholz
2005-06-09 13:10 ` foser
2005-06-09 16:49 ` Maurice van der Pot
2005-06-07 11:23 ` Simon Stelling
2005-06-07 14:04 ` Aron Griffis
2005-06-07 14:20 ` Diego 'Flameeyes' Pettenò
2005-06-07 15:15 ` Aron Griffis
2005-06-07 15:30 ` Diego 'Flameeyes' Pettenò
2005-06-07 22:35 ` Chris Gianelloni
2005-06-07 16:49 ` Michael Cummings
2005-06-07 18:38 ` Aron Griffis
2005-06-07 22:31 ` Chris Gianelloni
2005-06-07 22:32 ` Diego 'Flameeyes' Pettenò
2005-06-07 21:32 ` Marcus D. Hanwell
2005-06-07 21:44 ` Aron Griffis
2005-06-07 21:56 ` Olivier Crete
2005-06-07 22:11 ` Marcus D. Hanwell
2005-06-07 23:58 ` Lars Weiler
2005-06-07 22:18 ` Aron Griffis
2005-06-09 13:01 ` foser
2005-06-08 14:44 ` Jason Wever
2005-06-08 15:39 ` Joseph Jezak
2005-06-08 16:18 ` Marcus D. Hanwell
2005-06-08 16:23 ` Jason Wever
2005-06-07 23:07 ` Ferris McCormick
2005-06-08 0:25 ` Donnie Berkholz
2005-06-08 13:15 ` Chris Gianelloni
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=20050606222623.GI9084@kaf.zko.hp.com \
--to=agriffis@gentoo.org \
--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