Comment # 6 on bug 1225784 from Daan De Meyer

> Why would one need them in a separate package? They shouldn't be needed at runtime, but only when building software, and I think they can only be used with Clang and not GCC. It should be noted that while compiler-rt is a separate subproject upstream, it's also upstream's choice to install it in %{_libdir}/clang.

Both are fine with me, I don't mind too much where the static libraries live,
as long as the shared libraries are subpackaged.

> Instead of $(clang --print-file-name="")lib/linux, better use $(clang -print-runtime-dir).

Thank you for the suggestion, I will give that a try.

> But it's not so nice that this has to be done manually, or that we need an RPATH at all. The only issue with adding SO numbers is that this is discouraged by our packaging guidelines, so I might just leave them in their directory for now. But this is also kind of against the guidelines, as these are not private libraries, but meant to be used by other applications. So they should probably live in %{_libdir}.

Frankly if you did this it would just make my life harder. Every other distro
ships these libraries in the private directory so I'd just have to add yet more
special casing to deal with openSUSE doing it differently. If you really want
to go this route I would suggest discussing this with all the other
distribution clang maintainers so this move can be done across distros instead
of only in openSUSE. Given the amount of work that would entail, I suggest just
following the other distributions here.