<div dir="ltr">Forgot to cross-post oe-devel...</div><div class="gmail_extra"><br><div class="gmail_quote">On 23 June 2015 at 15:30, Ross Burton <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Yes, I'm bringing this up again. :)<br>
<br>
Our default of libexecdir=$libdir/$BPN is contrary to both the FHS[1] and GNU<br>
Coding Standards[2], mainly because the key point is that libexecdir should be<br>
global and not change per-recipe. The new FHS allows /usr/libexec so this<br>
series changes the default to that, and fixes up the recipes which need fixing.<br>
<br>
Several of the recipe fixes are unrelated to the change and will be submitted to<br>
master shortly, but others (eg sudo) are intimately tied to the change.<br>
<br>
I've done basic multilib-enabled builds but more testing welcome. I'd say that<br>
in general multilib problems this exposes are in fact problems with the recipe:<br>
for example GConf should install the binaries once and libraries in each libdir.<br>
<br>
Ross<br>
<br>
[1] <a href="http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html" rel="noreferrer" target="_blank">http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html</a><br>
[2] <a href="https://www.gnu.org/prep/standards/html_node/Directory-Variables.html" rel="noreferrer" target="_blank">https://www.gnu.org/prep/standards/html_node/Directory-Variables.html</a><br>
<br>
</blockquote></div><br></div>