<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 6 May 2014 10:49, Richard W.M. Jones <span dir="ltr"><<a href="mailto:rjones@redhat.com" target="_blank">rjones@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Tue, May 06, 2014 at 04:11:50PM +0200, Miloslav Trmač wrote:<br>
</div><div class="">> 2014-05-06 16:06 GMT+02:00 David Cantrell <<a href="mailto:dcantrell@redhat.com">dcantrell@redhat.com</a>>:<br>
><br>
> > I think the annoying thing is if you're typing out a path that includes<br>
> > /usr/lib, you can't easily hit TAB to get in to lib. And that's worth<br>
> > fixing.<br>
> ><br>
><br>
> Oh my...<br>
><br>
> 1) With the existence of /usr/lib{,64}, the additional existence of<br>
> /usr/libexec doesn't make any difference AFAICT.<br>
<br>
</div>Well getting rid of /usr/lib64 and multilib would be another<br>
worthwhile long-term goal. Debian have used a more sensible scheme:<br>
<br>
<a href="https://wiki.debian.org/Multiarch" target="_blank">https://wiki.debian.org/Multiarch</a><br>
<br>
For entertainment:<br>
<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=235752" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=235752</a><br>
<br></blockquote><div><br></div><div>I would go through the Debian bug system to find all the issues they have with their multiarch scheme and certain software. Both 'solutions' cause issues at time and headaches for packagers to sysadmins to users. Now whether or not one set of headaches/problems is less painful I don't know.. [I only know this because the one thing my Debian friends ever tell me that Red Hat got right was with multilib versus multiarch ... of course they could just be throwing me a bone.]</div>
</div><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>