On Sat, May 27, 2006 at 11:14:44AM -0700, Tyler MacDonald wrote: > Sune Vuorela <nospam@vuorela.dk> wrote: > > > Odd, because my package depends on libapr0-dev (probably going to be > > > libapr0-dev | libapr1-dev soon), and an apt-cache search for "0-dev" on my > > The versionings is when stuff change to incompatible APIs, so probably > > depending on (libfoo0-dev | libfoo1-dev) should not be possible. > > If there is no change in APIs, there is no need for versioning of the > > -dev package. > > You can alwayls add a versioning number on api-change. > In APR's case, there are some small incompatibilities in the APIs > between version 0 and version 1, but many packages can still compile > successfully against either. > And yeah, in libbttracker, etc.'s case, I don't plan on changing the > soname until there's an incompatibility. You're missing the point that sonames track *ABI* changes, and -dev package names should track *API* changes. Typically, upstreams make API changes on new major releases; ABI changes can happen much more often than this. Tracking sonames in your -dev package names is therefore wrong and (inevitably, eventually) causes gratuitous churn for any packages build-depending on yours. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature