Inter-library dependencies

[naddy_(_at_)_mips_(_dot_)_inka_(_dot_)_de (Christian Weisgerber)]

We need to develop a firm policy on inter-library dependencies.

Linking shared libraries against each other appears to be rapidly
becoming the standard way to do things for Linux-based developers.
We need to decide whether we want to go along with that.  On the
plus side, we wouldn't have to change builds all over (the libraries
themselves, dependent code).  On the minus side, static linking would
still require those changes or break.

If we want to convince upstream developers to stop linking shared
libraries against each other, we'll need a well-crafted argument.
"It breaks static linking, which is all we got on our legacy archs"
will only get us laughed at.  There may be other arguments, I don't
know.

If we decide that we do not want inter-library dependencies, it
would be best if our dynamic linker didn't support them, because
otherwise the rule will be next to impossible to enforce.  It will
also cause a world of pain for porters.

Either way, the current policy of "we don't want that, but we don't
really enforce it, and maybe it's okay for KDE" is not helpful.

-- 
Christian "naddy" Weisgerber                          naddy_(_at_)_mips_(_dot_)_inka_(_dot_)_de