| 1 |
On 21/03/13 14:10, Peter Stuge wrote: |
| 2 |
> Samuli Suominen wrote: |
| 3 |
>>> Samuli Suominen wrote: |
| 4 |
>>>> it should always be enabled with 'kernel_linux' and let the |
| 5 |
>>>> application itself do a runtime check if inotify is available or not |
| 6 |
>>> |
| 7 |
>>> I think it's great if you are working on such patches for upstreams! |
| 8 |
>> |
| 9 |
>> no, i'm talking from experience -- every package I've seen/touched/... |
| 10 |
>> with IUSE="inotify" has had code that made it safe to use also for |
| 11 |
>> non-inotify'd kernels |
| 12 |
>> i'm referring to the mistakes done by maintainers by adding |
| 13 |
>> unnecessarily the flag |
| 14 |
> |
| 15 |
> That was not at all clear, but that's great! Then you could fix those |
| 16 |
> ebuilds. |
| 17 |
|
| 18 |
Yes, I could, or I could just let other maintainers know about it, like |
| 19 |
on the ML, wait... that's what I just did |
| 20 |
|
| 21 |
> Except there's that rule to not fix bugs in others' ebuilds, |
| 22 |
> so even though you've found a bug you're not allowed to fix it.. :\ |
| 23 |
|
| 24 |
You cut down the important bit from my last post about 'cutting the sarcasm' |
| 25 |
We really don't need this in the ML |
| 26 |
Can we stop it before it begins? I hope so |
| 27 |
|
| 28 |
- Samuli |
Archives