From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Some ideas on how to reduce territoriality
Date: Mon, 06 Aug 2007 12:16:22 -0700 [thread overview]
Message-ID: <1186427782.8562.2.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <46B3D29F.5030301@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
On Fri, 2007-08-03 at 21:13 -0400, Luis Francisco Araujo wrote:
> > - arch-specific patches/dependencies - If someone is requesting KEYWORD
> > changes on a package and it requires a patch or additional dependencies
> > for your architecture, you are not only permitted, but really are
> > required to make the necessary changes to add support for your
> > architecture.
>
> I am not sure about this last one ... what if for example this patch is
> only for supporting a special option of the package for that
> architecture, but the maintainer of the package found out that such a
> patch is unnecessary and/or will cause other kind of problems in the
> package, therefore preferring avoiding such a patch ... or he just
> wouldn't like to apply the patch for X or Y; or even further, he just
> wouldn't like to have such a package available for that architecture
> just yet for Z or W.
The vagueness made it kinda hard to follow, but if a maintainer doesn't
want their package on an architecture, they need to mark it -arch for
that architecture. As it is right now, any arch team can add ~arch
without maintainer consent.
> The stabilization idea sounds good and it could free maintainers from
> filing similar bugs over and over ; but wouldn't this be more and harder
> work for arch teams?. For example, they should carefully track the
> history of all the packages to know when and if they should stabilize it
> yet.
Huh?
It's simple. The maintainer says "stabilize foo-1.2-r1" which gives a
minimum level that all arches should be using. If foo-1.2-r2 comes out,
it is up to the arch team to decide if/when to stabilize it, *unless*
the maintainer requests a newer version/revision. Basically, the
maintainer sets the minimum level they would like stable.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-06 19:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:06 [gentoo-dev] Some ideas on how to reduce territoriality Chris Gianelloni
2007-08-03 22:19 ` Mike Doty
2007-08-03 22:47 ` Chris Gianelloni
2007-08-04 7:21 ` Marius Mauch
2007-08-03 22:23 ` Philipp Riegger
2007-08-03 22:34 ` Petteri Räty
2007-08-03 22:40 ` Donnie Berkholz
2007-08-03 23:03 ` Mike Doty
2007-08-03 23:06 ` Mike Doty
2007-08-03 23:20 ` Robin H. Johnson
2007-08-04 14:43 ` [gentoo-dev] Commitlog-mailinglist (was: Re: Some ideas on how to reduce territoriality) Lars Weiler
2007-08-04 19:32 ` [gentoo-dev] Commitlog-mailinglist Donnie Berkholz
2007-08-06 9:41 ` [gentoo-dev] Commitlog-mailinglist Christian Faulhammer
2007-08-06 12:23 ` [gentoo-dev] Commitlog-mailinglist (was: Re: Some ideas on how to reduce territoriality) Mike Frysinger
2007-08-06 14:43 ` [gentoo-dev] Commitlog-mailinglist Lars Weiler
2007-08-06 15:01 ` Ned Ludd
2007-08-06 15:48 ` Lars Weiler
2007-08-06 16:20 ` Petteri Räty
2007-08-03 22:43 ` [gentoo-dev] Some ideas on how to reduce territoriality Philipp Riegger
2007-08-03 22:23 ` Petteri Räty
2007-08-03 22:49 ` Chris Gianelloni
2007-08-04 7:36 ` Marius Mauch
2007-08-03 22:53 ` Roy Marples
2007-08-04 1:13 ` Luis Francisco Araujo
2007-08-06 19:16 ` Chris Gianelloni [this message]
2007-08-07 3:48 ` [gentoo-dev] " Steve Long
2007-08-04 9:06 ` [gentoo-dev] " Alec Warner
2007-08-04 16:29 ` [gentoo-dev] " Steve Long
2007-08-04 17:17 ` Martin Jackson
2007-08-04 17:27 ` [gentoo-dev] " Jeroen Roovers
2007-08-04 17:39 ` Vlastimil Babka
2007-08-04 17:56 ` Steev Klimaszewski
2007-08-04 20:05 ` Petteri Räty
2007-08-04 23:56 ` Jurek Bartuszek
2007-08-05 6:27 ` Jeroen Roovers
2007-08-06 12:26 ` Mike Frysinger
2007-08-06 16:18 ` Petteri Räty
2007-08-07 0:23 ` Mike Frysinger
2007-08-05 0:03 ` [gentoo-dev] " Steve Long
2007-08-05 7:50 ` Petteri Räty
2007-08-04 19:34 ` Tiziano Müller
2007-08-05 0:19 ` Steve Long
2007-08-05 16:14 ` [gentoo-dev] " Ciaran McCreesh
2007-08-06 14:09 ` [gentoo-dev] " Steve Long
2007-08-06 9:24 ` Christian Faulhammer
2007-08-06 11:16 ` [gentoo-dev] " Paul de Vrieze
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=1186427782.8562.2.camel@inertia.twi-31o2.org \
--to=wolf31o2@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