Comment 14 for bug 527142

We sometimes bundle libraries when they are guaranteed to change SONAME at the same time and upstream makes good uses of SONAMES, libglib2.0-0 is one example. This has to be decided on a case-by-case basis. Don't look too closely at the library packaging guide, it's relatively old and never was a consensual document.

After taking a look at the source, it seems like the libs are entirely different in this case and aren't particularly expected to share a SONAME. I was a bit surprized that the ChangeLog doens't mention any SONAME change, either this has been perfectly designed or this didn't change for a long time or the SONAME change was forgotten.

Some of the libs look like convenience libs, but I'm not familiar enough to judge.

Given that only 4 packages build-dep on libcluster-glue-dev, I'm tempted to think that this is a case of an upstream providing all the clients for the libs, and releasing updates in lockstep. Perhaps this is an indication that some tighter versioning should be enforced, either by matter of symbol files (which are really missing here) or via "dh_makeshlibs -V". The latter seems easy to add and likely to prevent accidents, it's pain at a larger scale though.