From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foser.warande.net (216pc222.sshunet.nl [145.97.222.216]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j5AEstOg009749 for <gentoo-dev@lists.gentoo.org>; Fri, 10 Jun 2005 14:54:55 GMT Received: from rivendell (rivendell.foser.warande.net [192.168.0.2]) by foser.warande.net (Postfix) with ESMTP id 3978736FA3 for <gentoo-dev@lists.gentoo.org>; Fri, 10 Jun 2005 16:59:21 +0200 (CEST) Subject: Re: [gentoo-dev] ekeyword and ordering From: foser <foser@gentoo.org> To: gentoo-dev@lists.gentoo.org In-Reply-To: <42A8653F.3060409@gentoo.org> References: <20050606222623.GI9084@kaf.zko.hp.com> <200506061841.11356.vapier@gentoo.org> <42A4D308.9030104@gentoo.org> <42A59038.4060108@gentoo.org> <42A60A72.10200@gentoo.org> <1118323176.29369.26.camel@rivendell> <42A8653F.3060409@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1gbOspa7Hs/V+9poG+1h" Date: Fri, 10 Jun 2005 16:55:17 +0200 Message-Id: <1118415317.13269.31.camel@rivendell> Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-Archives-Salt: a038aa13-bba8-434d-8bdc-a2c9ba14adaf X-Archives-Hash: 753da3d665b2c140039d14d7a512a78d --=-1gbOspa7Hs/V+9poG+1h Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2005-06-09 at 11:50 -0400, Stephen P. Becker wrote: > Whoever said we were voting? I was just showing my support for > alphabetical keyword ordering. Remember, alphabetical keywording is > *already* implemented in ekeyword, and we are discussing whether or not > to revert it.=20 As the threadstarter indicated, this was done without discussing it and in the knowledge that there was no agreement on this issue. As said before, the fact that something gets done some way, doesn't mean it's right to do it that way. > foser-- In the response to that particular expression -especially by the 'guys' implied- you can see at least you try to defend your position now, that's more discussion like. > If everyone starts using ekeyword now with the alphabetical ordering > built in, everything will be consistent, and there shouldn't be a problem= . See earlier replies : unneeded arbitrarily introduced inconsistency. I don't know why people are defending that move, even vapier indicates that there really is no reason to do it alphabetically, except maybe that he now knows to look in the keywords string, which is of course a bit far fetched with all arch keywords not being set for all different packs (so he still has to look at different points in different packs) and was not brought up as a defence of his particular move at the time he started doing this. > I guess by "creating more traffic" you mean the one time when updating > the ebuilds with the new ordering during rsync for each user. Even if > this is significant over the whole tree, once everything is updated with > keyword ordering and everyone has done an emerge sync, there won't be > any more trouble, and we can just stay happy with the consistent > alphabetical ordering enforced by ekeyword. Oh no doubt, I'm concerned about the inconsistency mostly. The maintainers arch is a concept that I do not necessarily associate with the keywords ordering anymore (although it may have been a reasonable indicator in the past), it actually really makes this discussion fuzzier than it has to be. My point is more about how this got 'introduced' as a mindset and that such unguided behaviour gets reinforced by this discussion, now up to IUSE ordering changes and next we'll tackle inheritance order. - foser --=-1gbOspa7Hs/V+9poG+1h Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBCqanV8WG+0iaGxDMRAsX+AJ9tFBsJxw1mhPjfogiMHv+OkqwBKACfc1kp M5DqtHHs+y+4jiZPsVhIF3U= =A1Qp -----END PGP SIGNATURE----- --=-1gbOspa7Hs/V+9poG+1h-- -- gentoo-dev@gentoo.org mailing list