From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Wed, 25 Aug 2004 23:49:47 -0500 [thread overview]
Message-ID: <1093495787.9888.14.camel@localhost> (raw)
In-Reply-To: <20040825212237.525af76a@voyager.weeve.org>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
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.
--
Donnie Berkholz
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-26 4:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:11 [gentoo-dev] Ebuild bumping policy wrt KEYWORDS Jason Wever
2004-08-25 3:00 ` Jason Wever
2004-08-25 15:30 ` Michael Kohl
2004-08-26 3:17 ` Jason Wever
2004-08-26 14:51 ` Carsten Lohrke
2004-08-26 15:04 ` Ciaran McCreesh
2004-08-26 15:30 ` Carsten Lohrke
2004-08-26 15:33 ` Ciaran McCreesh
2004-08-26 16:11 ` Travis Tilley
2004-08-31 13:07 ` foser
2004-09-01 2:09 ` Travis Tilley
2004-09-01 10:06 ` foser
2004-09-01 16:30 ` Robert Moss
2004-09-01 23:15 ` Carsten Lohrke
2004-09-01 23:20 ` Ciaran McCreesh
2004-09-01 23:42 ` Carsten Lohrke
2004-08-26 16:27 ` Carsten Lohrke
2004-08-31 13:23 ` foser
2004-08-25 13:51 ` Chris Gianelloni
2004-08-26 3:22 ` Jason Wever
2004-08-26 4:49 ` Donnie Berkholz [this message]
2004-08-26 5:20 ` Jason Wever
2004-08-26 6:19 ` Donnie Berkholz
2004-08-26 14:16 ` Chris Gianelloni
2004-08-26 14:44 ` Ciaran McCreesh
2004-08-26 15:02 ` Chris Gianelloni
2004-08-26 15:31 ` Jason Wever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1093495787.9888.14.camel@localhost \
--to=spyderous@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox