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 1613D198005 for ; Thu, 21 Mar 2013 12:28:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 18E30E0782; Thu, 21 Mar 2013 12:27:40 +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 4AF43E076C for ; Thu, 21 Mar 2013 12:27:23 +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 1C24A33BF3D for ; Thu, 21 Mar 2013 12:27:05 +0000 (UTC) Message-ID: <514AFC6B.9090004@gentoo.org> Date: Thu, 21 Mar 2013 14:26:19 +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> <514AF6E7.9090703@gentoo.org> <20130321121007.8615.qmail@stuge.se> In-Reply-To: <20130321121007.8615.qmail@stuge.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 1b7aa0b4-c444-4dcf-ae80-f8329baf305e X-Archives-Hash: 58b44290daf100e0f99c33513d35462a 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