Re: dh_shlibdeps in = warnings; dh_shlibdeps out = cyclic dependency on self

[Justin Pryzby <justinpryzby@users.sourceforge.net>]

On Tue, Sep 06, 2005 at 11:17:44AM -0400, pryzbyj wrote:
> On Tue, Sep 06, 2005 at 01:10:11PM +0300, Eddy Petri?or wrote:
> > Hello all,
> Good morning,
> 
> > - the compile generates a set of 3 libqingy* files; do I have to make
> > a libqingy package, too?
> It seems that these are probably not meant to be used by other
> applications, correct?  Are the 3 files .a, .so, and .so.0, or are
> there 3 libquingy-$foo.so files, for 3 different values of $foo?
> 
> My understanding is that you should not provide a separate library
> package if the libraries are just internal to the program, and are not
> meant to be used by others.  If they _are_ meant to be used by others
> (other developers, and other packages, potentially), then my
> understanding is that you should provide a separate libquingy package
> (and a libquingy-dev which contains just the libquingy.a, the
> libquingy.so => libquingy.so.0 symlink for compilation, and the
> quingy.h header).
> 
> Are there multiple binaries in your package?  If not, then you should
> probably just link the library statically into the single binary,
> which resolve the whole issue anyway.  There was a -mentors thread
> about this about 6 months ago.
I was referring to this thread:

  http://lists.debian.org/debian-mentors/2005/01/msg00469.html

> Justin