| 1 |
On Sun, Mar 3, 2013 at 7:49 AM, Carlos Silva <r3pek@×××××.org> wrote: |
| 2 |
> On Sun, Mar 3, 2013 at 1:42 PM, hasufell <hasufell@g.o> wrote: |
| 3 |
>> |
| 4 |
>> What do we have useflags for in gentoo? |
| 5 |
>> |
| 6 |
>> add a "unsupported-kernels" useflag, mask it, add a clear statement in |
| 7 |
>> the masking reason and be done |
| 8 |
> |
| 9 |
> |
| 10 |
> Not a bad solution, still, I, as a user, don't think making the compilation |
| 11 |
> work with a specific kernel should be considered "unsupported". How many |
| 12 |
> times modules stop working because the kernel changed something that breakes |
| 13 |
> compilation? And I'm not only talking about closed source drivers, even |
| 14 |
> open source ones have this "problem", but in fact, they are fixed faster. |
| 15 |
> |
| 16 |
> Does the gentoo community really need this kind of strictness? Don't think |
| 17 |
> so. |
| 18 |
> |
| 19 |
|
| 20 |
So I'm going to get a bit meta here, forgive me ;) |
| 21 |
|
| 22 |
Currently the project more or less functions on herd and maintainer |
| 23 |
'ownership.' Ownership of problems tends to be good in many cases. It |
| 24 |
is clear who is responsible, we know who to contact to fix bugs and |
| 25 |
ask questions of. This does lead to disagreements (such as this |
| 26 |
thread.) Some developers want these patches and the package |
| 27 |
maintainers disagree. In the current scheme, the package maintainer |
| 28 |
always wins. This is the downside to ownership, ownership implies |
| 29 |
control and responsibility. The package maintainers are against these |
| 30 |
patches, they do not want to own them, and they do not want the |
| 31 |
associated responsibility of users using them. |
| 32 |
|
| 33 |
I don't even necessarily mind Samuli's commit (ask for forgiveness, |
| 34 |
not permission), but I would mind if he put the patches back. The |
| 35 |
package maintainer has spoken out about why they dislike the patches |
| 36 |
and you should respect their opinion. The maintainers in this case |
| 37 |
suggested an overlay, and they even offered point users to it. |
| 38 |
|
| 39 |
This is the system we have; if you think it sucks (and it does, |
| 40 |
sometimes) please propose something better. |
| 41 |
|
| 42 |
-A |
Archives