On Tue, Jul 17, 2012 at 06:44:00PM -0500, William Hubbs wrote:
> On Tue, Jul 17, 2012 at 01:46:17PM +0200, Tom Gundersen wrote:
> > We had a similar issue in Arch. What we did was the following:
> >
> > Patch udev+kmod+systemd (the last one was for free) to read from
> > {/usr,}/lib/{modprobe.d,depmod.d,udev/rules.d,systemd/system}.
> >
> > We then rebuild all the packages that installed binaries to /lib/udev/
> > and /lib/systemd to move them to their /usr/lib counterparts (as we
> > did not want to patch udev/systemd to read the helpers from more than
> > one location).
> >
> > Then we let people rebuild their packages to move things from /lib to
> > /usr/lib on a package-by-package basis.
> >
> > Then we rebuilt all our kernels and pointed kmod/udev to
> > /usr/lib/modules rather than /lib/modules.
> >
> > At this point only glibc owned stuff in /lib, so we rebuilt that to
> > move it all to /usr/lib and replace /lib with a symlink to /usr/lib.
>
> The problem for us with these steps is that the building happens on
> users' systems since we are source based, so we have to go about it
> differently. We can't rebuild packages and send them down to the users.
No, but we can fix all packages in the tree, and then update the udev
version, with a big fat warning / error when we install the new udev
package saying that the rules need to be fixed by updating the packages
that placed them there.
> This is why it would be very helpful if udev would keep some backward
> compatibility and read rules from /lib/udev/rules.d as long as it was a
> directory.
I don't think this is really necessary, as long as we just fix up all
packages in the tree that are doing things wrong. That shouldn't take
very long (hint, if you need help, I'll be glad to do so.)
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
