From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j58GMT5q011086 for ; Wed, 8 Jun 2005 16:22:29 GMT Received: from stargazer.weeve.org ([24.8.204.228]) by comcast.net (sccrmhc11) with SMTP id <2005060816230801100f15vve>; Wed, 8 Jun 2005 16:23:08 +0000 Date: Wed, 8 Jun 2005 10:23:04 -0600 (MDT) From: Jason Wever To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] ekeyword and ordering In-Reply-To: <42A7111B.5040306@gentoo.org> Message-ID: References: <20050606222623.GI9084@kaf.zko.hp.com> <200506072232.36536.cryos@gentoo.org> <20050607214457.GH19249@kaf.zko.hp.com> <42A7111B.5040306@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: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archives-Salt: e810a97b-9d85-4039-a746-5ef3f735a20f X-Archives-Hash: 839449f64507bf12b3ec98dbc0b39717 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 8 Jun 2005, Joseph Jezak wrote: >> Agreed, the PPC team is very good at arbitrarily marking things stable >> whenever they feel like it, and often times before the maintainer does. > > This is not usually our policy. However, because we moved GCC-3.4 to > stable before many arches, there were a number of packages that needed > to be marked stable for PPC in order for the stable version to even > compile. What should we have done in this case then? Assuming there wasn't a very compelling, "stuff is horribly broken in gcc-3.3.x" type reason, wait for the maintainer arch. - -- Jason Wever Gentoo/Sparc Co-Team Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCpxtqdKvgdVioq28RAjm7AJ9psRHMb8LYB6KqAhdi/jAzKj2j8ACglq3s s8L6J7Ims/ZPt6upqMrgtlU= =M1Z0 -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list