From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A6479198005 for ; Thu, 21 Mar 2013 12:10:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C8179E06B1; Thu, 21 Mar 2013 12:10:10 +0000 (UTC) Received: from foo.stuge.se (foo.stuge.se [212.116.89.98]) by pigeon.gentoo.org (Postfix) with ESMTP id 88C28E0678 for ; Thu, 21 Mar 2013 12:10:08 +0000 (UTC) Received: (qmail 8616 invoked by uid 501); 21 Mar 2013 12:10:07 -0000 Message-ID: <20130321121007.8615.qmail@stuge.se> Date: Thu, 21 Mar 2013 13:10:07 +0100 From: Peter Stuge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Make inotify a global USE flag? Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20810.57629.196394.526922@a1i15.kph.uni-mainz.de> <514AE1BF.3030605@gentoo.org> <20810.57629.196394.526922@a1i15.kph.uni-mainz.de> <20130321114356.6340.qmail@stuge.se> <514AF6E7.9090703@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <514AF6E7.9090703@gentoo.org> X-Archives-Salt: 5a9e2cf6-2836-4292-be5a-072f9d1c2ef7 X-Archives-Hash: 77746f629744d4f0e14837f019a03799 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. 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.. :\ //Peter