1 |
Fabian Groffen wrote: |
2 |
> On 06-11-2009 19:48:16 +0530, Nirbheek Chauhan wrote: |
3 |
>> On Fri, Nov 6, 2009 at 1:42 AM, Petteri Räty <betelgeuse@g.o> wrote: |
4 |
>>> In the past when smaller arches were not that active we used to mark |
5 |
>>> Java packages stable after testing by at least one arch team. The |
6 |
>>> probability to find arch specific issues in something like Java is not |
7 |
>>> so high so I think arrangements like this are acceptable when the arch |
8 |
>>> teams have problems keeping up. |
9 |
>> I think the same should be extended to other languages such as Perl |
10 |
>> and Python (unless they have portions which are C/C++) |
11 |
> |
12 |
> Sounds like we could benefit from the "noarch" approach known in the RPM |
13 |
> world, such that all these packages can also be immediately keyworded |
14 |
> and stabilised for all arches. Would greatly simplify things for a |
15 |
> great deal of packages, maybe? |
16 |
|
17 |
We could introduce "noarch" and "~noarch" KEYWORDS, add "noarch" to |
18 |
the default ACCEPT_KEYWORDS setting for all profiles, and instruct |
19 |
unstable users to add "~noarch" to ACCEPT_KEYWORDS. |
20 |
-- |
21 |
Thanks, |
22 |
Zac |