Bug#863030: Do not encode soversion in source and dev package name

[Michael Biebl]

Am 20.05.2017 um 14:17 schrieb Michael Biebl:

> Please consider renaming the source package to
> Source: libidn2 so it reflects the upstream name
> and the dev package to
> Package: libidn2-dev

Reasons for *not* including the soversion in the -dev package name:
- On a soname bump, you most likely have a  file conflict with the old
dev package, you they are not co-installable anyway and you need Conflicts.

While you currently have the soversion in then source package name, you
could potentially ship multiple versions in the archive, but you
actually don't want multiple versions to pile up.
It's more straightforward to rebuild all reverse dependencies and fix
the few which might FTBFS.

- There's less package churn. Having to update all reverse dependencies
to use libidn2-1-dev instead of libidn2-0-dev is cumbersome.


Thankfully, switching to an unversioned libidn2-dev package name at this
point would be rather simple as only three packages currently build
against libidn2:

curl: libidn2-0-dev
html-xml-utils: libidn2-0-dev
wget: libidn2-0-dev



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc
Description: OpenPGP digital signature