From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6750 invoked from network); 26 Aug 2004 06:22:15 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 26 Aug 2004 06:22:15 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1C0DeI-0001I6-RB for arch-gentoo-dev@lists.gentoo.org; Thu, 26 Aug 2004 06:22:14 +0000 Received: (qmail 29989 invoked by uid 89); 26 Aug 2004 06:22:14 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 15345 invoked from network); 26 Aug 2004 06:22:13 +0000 Message-ID: <412D81CC.6070307@gentoo.org> Date: Thu, 26 Aug 2004 02:23:08 -0400 From: Travis Tilley User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040811) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Content-Type: multipart/mixed; boundary="------------020509000707000901070006" Subject: [Fwd: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS] X-Archives-Salt: a090e29b-d839-4fc1-8ca1-3619463d6540 X-Archives-Hash: 72b9e0257d510fa768ee3b7d519c5e60 --------------020509000707000901070006 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit i sent this just to spyderous by accident. oops. ^^; --------------020509000707000901070006 Content-Type: message/rfc822; name="Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS" Message-ID: <412D7260.9070806@gentoo.org> Date: Thu, 26 Aug 2004 01:17:20 -0400 From: Travis Tilley User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040811) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Donnie Berkholz Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS References: <1093441861.31835.9.camel@cgianelloni.nuvox.net> <20040825212237.525af76a@voyager.weeve.org> <1093495787.9888.14.camel@localhost> In-Reply-To: <1093495787.9888.14.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Donnie Berkholz wrote: > On Wed, 2004-08-25 at 22:22, Jason Wever wrote: > >>According to >>http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_chap2, >>if an ebuild had an ~arch or arch keyword in the previous version, the >>policy is to make it ~arch in the new version. If for some reason the >>package maintainer is of the impression the new version would break a >>given arch, they may omit the arch from the new version and request the >>arch test out the package. > > > I also would hesitate to auto-~arch fairly critical packages, such as X > or anything in system. whoa whoa whoa, you better ~amd64 keyword --all-- of that, there are enough ebuilds in the tree to test for stabilisation without having to realise when something was ripped out of your arch entirely. ayanami portcvs # find *-* -type d -mindepth 1 -maxdepth 1 | while read d; do grep -q '^KEYWORDS.*~amd64' $d/*.ebuild && ! grep -q '^KEYWORDS.*[^~]amd64' $d/*.ebuild && echo $d; done > ./testing-only ayanami portcvs # cat testing-only | wc -l 1315 maybe your idea would make some sense on x86, where the job of stabilisation is that of the package maintainer... but it would be quite a bit more difficult to implement anywhere else. ~arch is expected to be somewhat rocky territory... that's why we have stable and testing seperate, no? Travis Tilley --------------020509000707000901070006 Content-Type: text/plain; charset=us-ascii -- gentoo-dev@gentoo.org mailing list --------------020509000707000901070006--