-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/07/12 01:01 AM, Ben de Groot wrote: > On 12 July 2012 07:42, William Hubbs <willi...@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? >
A symlink isn't a good idea as, iirc, the new udev still -reads- from both /usr/lib/udev and /lib/udev .. so it'd have two sources for the exact same rules; could be an issue. Given this, the way I see it all we need is a helper s.t. all installs going forward put the rules into the right place according to the installed udev (or maybe the installed virtual/device-manager) so that ebuilds/packages dont need to worry about setting the paths explicitly; and eventually as things progress all the rules in /lib/udev will get cleaned out in favour of /usr/lib/udev ... ? We could always just forgo the helper and make all packages migrate via a >=udev-186-r1 dep and setting the rules install paths explicitly to /usr/lib/udev ... the helper (to me) just makes this cleaner in the ebuild.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAk/+1J0ACgkQ2ugaI38ACPAaRgEAuknxIx3LOgVniVsEqxrwWfnj vNW5Zc/6/ZCn8QL+LZ8A/iepdgiZ7bmYtUb+Zj537o46z/prXP290q6oo/2DQy2j =G32M -----END PGP SIGNATURE-----
