Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
List Archive: gentoo-dev
| Navigation: |
|
Lists:
gentoo-dev:
< Prev
By Thread
Next >
< Prev
By Date
Next >
|
| Headers: |
|
To:
|
Gentoo Development <gentoo-dev@g.o>
|
|
From:
|
Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o>
|
|
Subject:
|
Re: Re: [RFC] Improve policy of stabilizations
|
|
Date:
|
Sat, 7 Nov 2009 04:36:51 +0100
|
|
2009-11-06 23:07:58 Zac Medico napisał(a):
> Fabian Groffen wrote:
> > On 06-11-2009 19:48:16 +0530, Nirbheek Chauhan wrote:
> >> On Fri, Nov 6, 2009 at 1:42 AM, Petteri Räty <betelgeuse@g.o> wrote:
> >>> In the past when smaller arches were not that active we used to mark
> >>> Java packages stable after testing by at least one arch team. The
> >>> probability to find arch specific issues in something like Java is not
> >>> so high so I think arrangements like this are acceptable when the arch
> >>> teams have problems keeping up.
> >> I think the same should be extended to other languages such as Perl
> >> and Python (unless they have portions which are C/C++)
> >
> > Sounds like we could benefit from the "noarch" approach known in the RPM
> > world, such that all these packages can also be immediately keyworded
> > and stabilised for all arches. Would greatly simplify things for a
> > great deal of packages, maybe?
>
> We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to
> the default ACCEPT_KEYWORDS setting for all profiles, and instruct
> unstable users to add "~noarch" to ACCEPT_KEYWORDS.
It seems to be a good idea, but I would prefer to use words "universal"
and "~universal" :) .
--
Arfrever Frehtes Taifersar Arahesis
|
| Attachment: |
|
signature.asc (This is a digitally signed message part.)
|
|