On Sat, Jan 22, 2011 at 12:02 PM, William Hubbs wrote:
> 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.
>
> I enquired from Robin why we do this, and I was told that libexec is
> supposed to contain things which are not abi specific, but we do not
> enforce that for /, even though we do for /usr.
>
> Is there a reason for this? If not, would it break things if we start
> using /libexec as well as /usr/libexec?
/libexec is also a horrible wart which we have avoided on purpose.
*BSD systems might use it, but we dont in Linux.
i dont think the multilib issue is terribly relevant unless the files
in question are used externally. with dhcpcd and openerc, the files
are only used internally, so keeping them in the native multilib dir
isnt an issue.
-mike
