From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: udev-rules.eclass
Date: Thu, 12 Jul 2012 09:47:33 -0400 [thread overview]
Message-ID: <4FFED575.5090607@gentoo.org> (raw)
In-Reply-To: <20120712091754.2480af4a@pomiocik.lan>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/07/12 03:17 AM, Michał Górny wrote:
> On Thu, 12 Jul 2012 13:01:21 +0800 Ben de Groot <yngwin@gentoo.org>
> wrote:
>
>> On 12 July 2012 07:42, William Hubbs <williamh@gentoo.org>
>> wrote:
>>> On Wed, Jul 11, 2012 at 10:57:42PM +0200, Diego Elio Pettenò
>>> wrote:
>>>> Il 11/07/2012 21:11, William Hubbs ha scritto:
>>>>> I am about to release udev-186-r1, which will move
>>>>> everything currently in /lib/udev to /usr/lib/udev.
>>>>
>>>> Unless you're going to establish a symlink, please keep it
>>>> under p.mask until everything is using some common code —
>>>> otherwise things _will_ break.
>>>
>>> Since multiple packages put things in /lib/udev, I'm not sure
>>> it is possible to establish a symlink from /lib/udev to
>>> /usr/lib/udev if that's what you mean; I'll look into it
>>> though.
>>
>> Couldn't you, on udev upgrade, move everything in /lib/udev to
>> /usr/lib/udev, and then make the symlink? Seems fairly simple to
>> me, but maybe I'm overlooking something?
>
> You are overlooking conflicts introduced through moving files
> without updating vardb.
>
There were no vdb issues when baselayout-1 was migrated to
baselayout-2, and it rewrote a whackload of stuff iirc...
Updating vdb shouldn't be an issue here, as long as pkg_postinst
doesn't crash mid-stream. Is the vdb common between package managers
or does each one have a different solution?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAk/+1XUACgkQ2ugaI38ACPBKdgD/S3jlct63PVIKE8UmHW4jEanZ
T2/lgnF/cUzTSlsyrEQA/iQWSvOcowsgI/r2VUlJLFpltNVea/f8pm5wKq5F4cjk
=HA5O
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-07-12 13:48 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 ` Ian Stakenvicius [this message]
2012-07-12 14:19 ` [gentoo-dev] " 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
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=4FFED575.5090607@gentoo.org \
--to=axs@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