Must a source package's shared libraries always be spit into separate binary packages?

To: debian-mentors@lists.debian.org
Subject: Must a source package's shared libraries always be spit into separate binary packages?
From: Sam Morris <sam@robots.org.uk>
Date: Mon, 19 Feb 2007 13:38:21 +0000 (UTC)
Message-id: <[🔎] erc98d$1sm$1@sea.gmane.org>

I am packaging the nemiver debugger, which has a new version that has
split some of its functionality into a libnemiver-common library. The
library is probably not very useful without nemiver itself being installed.

Is it ok to avoid splitting out a separate libnemiver-common0 package, and
instead ship the library file in the nemiver binary package?

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078

Reply to:

Follow-Ups:
- Re: Must a source package's shared libraries always be spit into separate binary packages?
  - From: "Paul Cager" <paul-debian@home.paulcager.org>

Prev by Date: Updating email address in an existing package.
Next by Date: Re: Must a source package's shared libraries always be spit into separate binary packages?
Previous by thread: Updating email address in an existing package.
Next by thread: Re: Must a source package's shared libraries always be spit into separate binary packages?
Index(es):
- Date
- Thread