public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Make inotify a global USE flag?
Date: Thu, 21 Mar 2013 14:26:19 +0200	[thread overview]
Message-ID: <514AFC6B.9090004@gentoo.org> (raw)
In-Reply-To: <20130321121007.8615.qmail@stuge.se>

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



  parent reply	other threads:[~2013-03-21 12:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 10:29 [gentoo-dev] Make inotify a global USE flag? Ulrich Mueller
2013-03-21 10:32 ` Samuli Suominen
2013-03-21 11:43   ` Peter Stuge
2013-03-21 12:02     ` Samuli Suominen
2013-03-21 12:10       ` Peter Stuge
2013-03-21 12:19         ` Sergey Popov
2013-03-21 12:26         ` Samuli Suominen [this message]
2013-03-21 13:33           ` Peter Stuge
2013-03-21 14:30             ` Tom Wijsman
2013-03-21 16:32   ` Michał Górny
2013-03-21 11:48 ` Alexander Berntsen
2013-03-21 14:14   ` Ulrich Mueller
2013-03-21 16:14     ` Alexander Berntsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=514AFC6B.9090004@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox