<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 12 December 2016 at 20:51, Mark Asselstine <span dir="ltr"><<a href="mailto:mark.asselstine@windriver.com" target="_blank">mark.asselstine@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2y2" class="a3s aXjCH m158f4cdff0c2f642">I think the discussion I pointed to in the commit log closes the door on any<br>
such change. Specific the comment from Lennart --<br>
<a href="https://github.com/systemd/systemd/issues/3810#issuecomment-235290526" rel="noreferrer" target="_blank">https://github.com/systemd/<wbr>systemd/issues/3810#<wbr>issuecomment-235290526</a><br>
<br>
They don't want the library to be found in the default search path, they want<br>
to maintain this as a "hidden, internal resource".</div></blockquote></div><br>Oh if it's an implementation detail of systemd and not a user-facing library then I can see their argument I guess.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Don't agree with it though. But, the point is that as long as the parts of systemd that could realistically be multilibd are in $libdir then this isn't a problem.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>