* [gentoo-dev] Re: Add a KEYWORD representing any arch
@ 2014-01-19 9:46 99% ` Ulrich Mueller
0 siblings, 0 replies; 1+ results
From: Ulrich Mueller @ 2014-01-19 9:46 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
>>>>> On Sun, 19 Jan 2014, Pacho Ramos wrote:
> El dom, 19-01-2014 a las 03:36 -0500, Mike Frysinger escribió:
>> you mean * ? this already works today (at least with portage):
>> KEYWORDS="~*"
>> KEYWORDS="*"
Currently not allowed by policy:
http://devmanual.gentoo.org/keywording/index.html
> I had no idea that existed :O, I guess something related with
> "specification" is missing? :/
Now what problem are we trying to solve? As I see it, it is mainly
one of manpower, namely that some arch teams cannot keep up with
stable requests, and I doubt that any technical solution will help
to solve this. Introducing a "noarch" keyword or allowing "*" will
potentially cause problems with dependency resolution.
Instead, we should come up with a clear set of rules under what
circumstances package maintainers are allowed to stabilise ebuilds
themselves on all architectures.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-01-14 21:37 [gentoo-dev] rfc: revisiting our stabilization policy William Hubbs
2014-01-17 6:06 ` grozin
2014-01-17 7:02 ` grozin
2014-01-19 8:36 ` Mike Frysinger
2014-01-19 9:28 ` Add a KEYWORD representing any arch (was: Re: [gentoo-dev] rfc: revisiting our stabilization policy) Pacho Ramos
2014-01-19 9:46 99% ` [gentoo-dev] Re: Add a KEYWORD representing any arch Ulrich Mueller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox