Re: soname number in name of dev-package?
- To: debian-devel@lists.debian.org
- Subject: Re: soname number in name of dev-package?
- From: Jens Peter Secher <jpsecher@get2net.dk>
- Date: Wed, 12 Jan 2005 21:29:15 +0100
- Message-id: <[🔎] 873bx6s86c.fsf@83.73.128.1.ip.tele2adsl.dk>
- In-reply-to: <3lWYE-6CE-7@gated-at.bofh.it> (Henning Makholm's message of "Wed, 12 Jan 2005 21:10:09 +0100")
- References: <3lWcg-5U4-3@gated-at.bofh.it> <3lWch-5U4-5@gated-at.bofh.it> <3lWch-5U4-7@gated-at.bofh.it> <3lWch-5U4-9@gated-at.bofh.it> <3lWch-5U4-11@gated-at.bofh.it> <3lWch-5U4-13@gated-at.bofh.it> <3lWcg-5U4-1@gated-at.bofh.it> <3lWYE-6CE-7@gated-at.bofh.it>
Henning Makholm <henning@makholm.net> writes:
> Scripsit Jens Peter Secher <jps@debian.org>
>
> > But the advice in the library packaging guide is to do something like
> > Package: libpackage2-dev
> > Provides: libpackage-dev
> > Conflicts: libpackage-dev
> > AFAICT the above approach offers nothing more than simply
> > Package: libpackage-dev
> > would do. Right?
>
> If the source-level API differs, then having libpackage2-dev will
> allow other packages to Build-Depend on the API they are written
> against. Of course this is especially relevant when the API change can
> make things break silently, but even outside that case, an explicit
> build-dependency is easier to diagnose (and/or search for mechanically
> over all packages in testing, say) than sudden compiler failures.
But that problem could just as well be solved by versioned
build-dependency on the -dev package, right?
--
Jens Peter Secher
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher get2net dk_
Reply to: