[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#368985: ITP: mod-bt -- BitTorrent tracker for the Apache2 web server

On Sat, May 27, 2006 at 06:02:07PM -0700, Tyler MacDonald wrote:
> Steve Langasek <vorlon@debian.org> wrote:
> > 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.

> 	OK, so it sounds like this is what you are saying:

> 	Since this is the first public API *and* ABI, both counters should
> start at zero.

> 	- When the API becomes incompatible (which would implicitly make the
> ABI incompatible), both the -dev and library package should increment their
> numbers.

> 	- When the ABI becomes incompatible without affecting the API, only
> the library package should increment it's number.

> 	Is that right?

With changing the package name on API changes being optional as well, since
API changes generally affect build-dependencies only, not dependencies, are
thus largely invisible to users, and in the general case don't tend to
happen in a way that justifies updates to all packages that would
build-depend on it.

But if you think you'll be making sufficient backwards-incompatible changes
to the library API to warrant such package name changes, yes, the above is
the right way to go about it.

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

Reply to: