public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [Fwd: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS]
@ 2004-08-26  6:23 Travis Tilley
  0 siblings, 0 replies; only message in thread
From: Travis Tilley @ 2004-08-26  6:23 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 53 bytes --]

i sent this just to spyderous by accident. oops. ^^;

[-- Attachment #2: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS --]
[-- Type: message/rfc822, Size: 2047 bytes --]

From: Travis Tilley <lv@gentoo.org>
To: Donnie Berkholz <spyderous@gentoo.org>
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Thu, 26 Aug 2004 01:17:20 -0400
Message-ID: <412D7260.9070806@gentoo.org>

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 <lv@gentoo.org>



[-- Attachment #3: Type: text/plain, Size: 37 bytes --]

--
gentoo-dev@gentoo.org mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-08-26  6:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-26  6:23 [Fwd: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS] Travis Tilley

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox