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

Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev



On Tue, 27 Oct 2015 10:06:50 +0100 Ansgar Burchardt <ansgar@debian.org> wrote:
> | If there are development files associated with a shared
> | library, the source package needs to generate a binary
> | development package named libraryname-dev, or if you
> | need to support multiple development versions at a time,
> | librarynameAPIVERSION-dev.

I'd suggest to additionally add *why* unversioned -dev packages are preferred:

| Note that using an unversioned package name like libraryname-dev
| often allows simpler transitions, because depending packages that
| just need recompilation against the new APIVERSION can be upgraded
| via binNMU, e.g. by the release team.

I'm new to packaging and it took a lot of asking around to find out about the *why* ;-)

> Ansgar

-- 
Yours sincerely,
Tim Janik

https://testbit.eu/timj/
Free software author and speaker.

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: