| 1 |
On 08/29/2013 01:02 AM, Ulrich Mueller wrote: |
| 2 |
>>>>>> On Wed, 28 Aug 2013, hasufell wrote: |
| 3 |
> |
| 4 |
>> No, it does not concern a single package only. This is about making |
| 5 |
>> a clear policy. There are more examples of packages with broken |
| 6 |
>> useflags such as app-editors/nano[debug] or other "vanilla" useflags |
| 7 |
>> for glibc and so on which are all in STABLE branch. |
| 8 |
> |
| 9 |
>> This was already discussed in #gentoo-qa and it seems there is no |
| 10 |
>> clear consensus about the issue. That's where the council has to |
| 11 |
>> make a call. |
| 12 |
> |
| 13 |
> As I said, get a resolution from QA first, before escalating to the |
| 14 |
> council. The procedure for this is clearly outlined in GLEP 48. |
| 15 |
> |
| 16 |
QA policy has always been "if it doesn't compile either fix it or mask it" |
| 17 |
|
| 18 |
I don't even see why this needs discussion. |
| 19 |
|
| 20 |
Do not expose users to breakage, OR ELSE (or else someone will fix it |
| 21 |
for you) |
Archives