Bug#568374: debian-policy: section "8.4 Development files" not explicit enough regarding libraryname[soversion]-dev
Control: tag -1 pending
Ansgar Burchardt <ansgar@debian.org> writes:
> I suggest to change
> | If there are development files associated with a shared
> | library, the source package needs to generate a binary
> | development package named librarynamesoversion-dev, or if you
> | prefer only to support one development version at a time,
> | libraryname-dev.
> to
> | 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.
> The changes are:
> Recommend unversioned -dev packages over versioned ones.
> For versioned -dev packages, use APIVERSION instead of SONAMEVERSION as
> API and ABI can change independently. This matches current practice: as
> a random example: libgweather-3-dev + libgweather-3-6
Thanks, applied for the next release.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: