From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j57E5XvL011091 for ; Tue, 7 Jun 2005 14:05:33 GMT Received: from agriffis by smtp.gentoo.org with local (Exim 4.43) id 1DfeiN-0005WC-HR for gentoo-dev@lists.gentoo.org; Tue, 07 Jun 2005 14:06:00 +0000 Date: Tue, 7 Jun 2005 10:04:31 -0400 X-OfflineIMAP-82243391-64676f73656e64-494e424f582e4f7574626f78: 1118153170-0308354995409-v4.0.8 From: Aron Griffis To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] ekeyword and ordering Message-ID: <20050607140431.GM9084@kaf.zko.hp.com> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20050606222623.GI9084@kaf.zko.hp.com> <42A583CD.2090201@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u/L2/WlOHZg+YGU4" Content-Disposition: inline In-Reply-To: <42A583CD.2090201@gentoo.org> User-Agent: Mutt/1.5.8i X-Archives-Salt: 385ffd3b-3695-4fb7-b37f-db3cbb2e5265 X-Archives-Hash: 21638dfad53f07b9e889176e85bbb2d1 --u/L2/WlOHZg+YGU4 Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Simon Stelling wrote:[Tue Jun 07 2005, 07:23:57AM EDT] > From [1]: > |When a package version has proved stable for sufficient time and the > |Gentoo maintainer of the package is confident that the upgrade will not > |break a regular Gentoo user's machine, then it can be moved from ~ARCH > |to ARCH. An indication of the package's stability would be no verified > |or unresolved bug report for a month after the version's introduction. >=20 > If that policy is dropped, I'd prefer alpha, otherways append. Could you explain why that policy needs to be dropped for alpha to be preferred? It's not obvious to me how that policy requires append. If all arch teams were to follow that policy, then it would work smoothly like this: 1. all keywords are ~arch 2. maintainer marks their arch(es) stable 3. arch maintainers see the stable marking (it could be any keyword in the list) and follow the leader In other words, you can implement "maintainer arch" with either alpha or append. The idea of putting the maintainer's arch first is purely cosmetic. Regards, Aron -- Aron Griffis Gentoo Linux Developer --u/L2/WlOHZg+YGU4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCpalvJrHF4yAQTrARAsDoAJ0de2oVDlvgLlKODxvlvfR67CJd6QCfZsl7 9409ANv6IiI7896y3Yw2Qs8= =eFnc -----END PGP SIGNATURE----- --u/L2/WlOHZg+YGU4-- -- gentoo-dev@gentoo.org mailing list