Comment 3 for bug 527195

Regarding the libraries in /usr/lib: a package was uploaded to maverick that split these out into a separate 'libpacemaker' binary package, which I rejected from the NEW queue. These libraries are *not* intended to be public; they appear to be nascent shared libs which nothing else should depend on yet, and for which standard shlibs maintenance cannot be assured.

I agree that these *should* be moved to /usr/lib/packemaker, to make it absolutely clear that they are private libraries. I would personally not regard this as a 'must'; AIUI there's no software in the wild that would attempt to link against these libs, and fixing this doesn't seem pertinent to an MIR as the bug remains one way or the other.

What *must* be fixed is that, if these are private libs, there should not be a shlibs control file in the package. This should be corrected, whether or not the package is promoted to main.