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