From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: udev-rules.eclass
Date: Wed, 11 Jul 2012 20:41:04 -0700 [thread overview]
Message-ID: <1342064464.14617.7.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <20120711234808.GB27226@linux1>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Wed, 2012-07-11 at 18:48 -0500, 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.
>
> This would have to be a rev bump for the broken packages.
>
> William
>
> >
> > A.
> >
So, does that mean the rule itself changes or just the location change
is needed?
If it is just a location change, a fairly simple udev-updater script
would do it. If the pkg needs to be re-compiled to work with/depend on
the new udev, then a more complex script would be needed. One more
along the line of python-updater/perl-cleaner.
--
Brian Dolbec <dolsen@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-07-12 3:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 19:11 [gentoo-dev] rfc: udev-rules.eclass William Hubbs
2012-07-11 19:57 ` W. Trevor King
2012-07-11 20:57 ` Diego Elio Pettenò
2012-07-11 23:42 ` William Hubbs
2012-07-11 23:43 ` Diego Elio Pettenò
2012-07-12 5:01 ` Ben de Groot
2012-07-12 5:26 ` Zac Medico
2012-07-12 7:17 ` Michał Górny
2012-07-12 7:33 ` Zac Medico
2012-07-13 6:29 ` [gentoo-dev] " Duncan
2012-07-12 13:47 ` [gentoo-dev] " Ian Stakenvicius
2012-07-12 14:19 ` Michał Górny
2012-07-12 14:34 ` Ian Stakenvicius
2012-07-12 14:37 ` Ciaran McCreesh
2012-07-12 13:43 ` Ian Stakenvicius
2012-07-12 14:20 ` Michał Górny
2012-07-12 14:34 ` Ian Stakenvicius
2012-07-12 15:02 ` Michał Górny
2012-07-11 20:57 ` William Hubbs
2012-07-11 20:59 ` Alexis Ballier
2012-07-11 23:48 ` William Hubbs
2012-07-12 2:25 ` Rick "Zero_Chaos" Farina
2012-07-12 2:50 ` Zac Medico
2012-07-12 3:03 ` Rick "Zero_Chaos" Farina
2012-07-12 16:42 ` Alexis Ballier
2012-07-12 3:41 ` Brian Dolbec [this message]
2012-07-12 16:30 ` Alexis Ballier
2012-07-13 5:44 ` Brian Dolbec
2012-07-12 16:24 ` Alexis Ballier
2012-07-11 21:51 ` Rick "Zero_Chaos" Farina
2012-07-12 14:22 ` Michał Górny
2012-07-12 14:35 ` William Hubbs
2012-07-12 19:58 ` Samuli Suominen
2012-07-12 20:31 ` Mike Gilbert
2012-07-12 21:04 ` Michał Górny
2012-07-12 21:01 ` Samuli Suominen
2012-07-12 21:09 ` Samuli Suominen
2012-07-12 21:39 ` [gentoo-dev] " Jonathan Callen
2012-07-13 18:12 ` [gentoo-dev] " William Hubbs
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=1342064464.14617.7.camel@big_daddy.dol-sen.ca \
--to=dolsen@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