Bug#700759: Shared library policy on private libs

[Sam Hartman <hartmans@debian.org>]

>>>>> "Phillip" == Phillip Susi <psusi@ubuntu.com> writes:

    Phillip> On 2/18/2013 1:21 PM, Sam Hartman wrote:
    >> 2) don't install a .so in a -dev package.

    Phillip> That might be a signal a human can understand, but the
    Phillip> build system won't catch it.  The goal is to make sure the
    Phillip> build system doesn't generate broken binary packages.

Uh, no.  If you don't install a .so, then linking with -lfoo won't work.

Not having a dev package tends to make it hard enough to link for 90% of
the cases.

with the current packaging tools, you tend to end up producing the
.shlibs files in order to manage cross-package dependencies within a
single source package.
If it were relatively easy  to convince the packaging tools to handle
dependencies within a source package and to omit including the shlibs
file in the binary, I'd buy that as a requirement too.

In general though I think including no headers and no .so for a library
makes a clear statement that build systems tend to respect:-)