From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.77) (envelope-from ) id 1SpMUP-0006Tx-4N for garchives@archives.gentoo.org; Thu, 12 Jul 2012 16:43:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57E5EE04F2; Thu, 12 Jul 2012 16:43:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 46488E049A for ; Thu, 12 Jul 2012 16:42:41 +0000 (UTC) Received: from localhost (unknown [200.89.69.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id 8C8071B4005 for ; Thu, 12 Jul 2012 16:42:37 +0000 (UTC) Date: Thu, 12 Jul 2012 12:42:21 -0400 From: Alexis Ballier To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: udev-rules.eclass Message-ID: <20120712124221.30a16235@gentoo.org> In-Reply-To: <4FFE3B82.6030807@gentoo.org> References: <20120711191142.GA26844@linux1> <20120711165911.1428ddb6@gentoo.org> <20120711234808.GB27226@linux1> <4FFE3588.1060101@gentoo.org> <4FFE3B82.6030807@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) 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-Transfer-Encoding: 7bit X-Archives-Salt: d1e92696-d1b2-4b78-b118-fb55b1a2e21a X-Archives-Hash: 509061c7d2f0b3bf8c9ed412f6efd056 On Wed, 11 Jul 2012 19:50:42 -0700 Zac Medico wrote: > On 07/11/2012 07:25 PM, Rick "Zero_Chaos" Farina wrote: > > On 07/11/2012 07:48 PM, William Hubbs wrote: > >> On Wed, Jul 11, 2012 at 04:59:11PM -0400, Alexis Ballier wrote: > >>> How do you plan to handle the following: > >>> - foo installs an udev rule > >>> - install foo with old udev > >>> - upgrade udev > >>> > >>> are rules installed by foo used by new udev ? > > > >> No, they wouldn't be; that is a good reason to question the value > >> of the eclass itself. Maybe the correct way to do this is to > >> forget the eclass and just file bugs against packages that break > >> having them move their rules to the new location and set a > >> dependency on the newer udev. > > Perhaps a new ebuild helper would be best here? It seems no one > > knows where to install udev rules in the first place (I know I > > didn't till a recent version of portage yelled at me with a QA > > warning). > > > > How about dorule/newrule? > > I guess then we'd need the installed udev to set an environment > variable via /etc/env.d, in order to control the location where the > rules are installed? Having the location of installed files depend on environment variables always sounded bad practices to me. Maybe it is quite common, but I remember specifically hardcoding paths in TeXLive's ebuilds/eclasses to avoid this behavior. A.