>Your -dev package went from libdcmtk2-dev to libdcmtk4-dev. That makes
> transitions too painful as every reverse dependency needs a sourceful upload
> to
> change the build dependency, instead of the release team just scheduling
> binNMUs
> as is normally done.
Here is how this is done:
[...]
Package: libdcmtk2-dev
Section: libdevel
Architecture: any
Depends: libdcmtk2v5 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
Conflicts: libdcmtk1-dev
Replaces: libdcmtk1-dev
Provides: libdcmtk-dev
[...]
So if third party libs requires explicit `libdcmtk2-dev`, then the
issue is within there own package. AFAIK there is nothing wrong with
this scheme.
