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 CC062198005 for ; Thu, 21 Mar 2013 12:03:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EE387E064B; Thu, 21 Mar 2013 12:03:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 16BACE062A for ; Thu, 21 Mar 2013 12:03:36 +0000 (UTC) Received: from [10.168.190.165] (85-76-13-167-nat.elisa-mobile.fi [85.76.13.167]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id C562A33D876 for ; Thu, 21 Mar 2013 12:03:34 +0000 (UTC) Message-ID: <514AF6E7.9090703@gentoo.org> Date: Thu, 21 Mar 2013 14:02:47 +0200 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Make inotify a global USE flag? 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> In-Reply-To: <20130321114356.6340.qmail@stuge.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: a24b325f-08a4-4bc7-a8bb-52c07299583a X-Archives-Hash: 7c4621092ab56d244c48130fbe73ea79 On 21/03/13 13:43, Peter Stuge wrote: > Ulrich Mueller wrote: >> Should we make it a global flag? > > Sure. > >> What description is better: >> >> inotify - Enable inotify filesystem monitoring support >> inotify - Enable inotify file change notification support > > The former is more correct, because inotify provides notifications > for more than just file changes. > > > 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 cut the sarcasm :-) - Samuli