Getting that discussion back on top. On Samstag, 22. Januar 2011, Diego Elio Pettenò wrote: > Il giorno sab, 22/01/2011 alle 11.02 -0600, William Hubbs ha scritto: > > Is there a reason for this? If not, would it break things if we start > > using /libexec as well as /usr/libexec? > > More or less and yes, it would create one more root directory that has > no real usage to be there anyway... > > > I noticed that for dhcpcd and openrc we force their LIBEXECDIR to be > > $(get_libdir)/foo, which puts things in different directories > > depending on whether the system is multilib or not. > > Which is wrong, it should be /lib/foo instead, not $(get_libdir), to > follow what udev and other software in Linux has been using for a very > long time now.
Sounds like we should fix udev ebuild and some ebuilds installing udev rules to not use /$(get_libdir)/udev, but plain /lib/udev. I used that in believe that /lib is identical or links to /$(get_libdir) and multilib-strict requires it, but it seems to be intelligent enough to only deny 64-bit libs to go to /lib. So proper udev should use /lib/udev, correct? Matthias
