| 1 |
On 01/13/2010 09:24 AM, Mike Frysinger wrote: |
| 2 |
> On Tuesday 12 January 2010 15:51:28 Tomáš Chvátal wrote: |
| 3 |
>> And since WE want to enable as-needed as default at some time we need to |
| 4 |
>> work on the bugs |
| 5 |
> |
| 6 |
> which isnt going to happen |
| 7 |
|
| 8 |
This isn't really intended to point fingers at anybody in particular - I |
| 9 |
haven't personally investigated the complexity of fixing the as-needed |
| 10 |
issue for this particular package. |
| 11 |
|
| 12 |
I think that logging as-needed bugs is certainly a value-add. |
| 13 |
|
| 14 |
I think that tracking a blocker for as-needed is a value-add. |
| 15 |
|
| 16 |
However, if we want to turn as-needed into a QA issue and try to enforce |
| 17 |
it, I think that this should really be run past the council and |
| 18 |
documented. It wouldn't hurt to also document tips for solving the |
| 19 |
problem and the proper way to mask as-needed if it just isn't going to |
| 20 |
work (even if we make as-needed the default that doesn't mean that we |
| 21 |
can't mask it if we have to). |
| 22 |
|
| 23 |
I think that devs should make good-faith efforts to fix as-needed |
| 24 |
issues, but if the problem is with the overall upstream design and major |
| 25 |
work is involved, that is an UPSTREAM problem. Sure, it is nice if |
| 26 |
somebody wants to be an upstream contributor and fix their problems for |
| 27 |
them, but I'm not sure that it is worth the Gentoo resources in every |
| 28 |
single case. Maybe for system packages or common dependencies we might |
| 29 |
push a little harder. |
| 30 |
|
| 31 |
In any case, when this kind of controversy exists the best solution is |
| 32 |
to make a proposal and ask the council to render a decision. It isn't |
| 33 |
productive to have battles on the mailing list about whether something |
| 34 |
should or shouldn't be policy. |
| 35 |
|
| 36 |
I don't mean to suggest that QA or treecleaners or whatever absolutely |
| 37 |
must run everything they do past the council. However, when we run into |
| 38 |
genuine disagreements between projects/herds/devs that is the ultimate |
| 39 |
escalation path. |
| 40 |
|
| 41 |
Package mask is not a very good way to try to hit devs with a cluestick |
| 42 |
anyway - the main victims of this sort of approach tend to be the users. |
Archives