Jan Kurik wrote:
* Other developers:
Maintainers, should
- Verify that their software is linked with the libidn library
- Update the software from upstream if it already has been converted to
libidn2
- Check the libidn2 instructions on converting a package to
libidn2.
- Propose patches (trivial task) to convert to libidn2, and
notify upstream about it.
In short switch software from libidn to libidn2, it is sufficient
replacing idna.h header with idn2.h.
I repeat again what I already wrote when this was initially announced,
because it was ignored:
I do not see why we need to patch each and every application for this. Since
the library is at least API-compatible (not sure about the ABI), libidn2-
devel should have Obsoletes and Provides for libidn-devel and symlinks
libidn.so → libidn2.so and idn.h → idn2.h. Then all that is needed in
application packages is a rebuild. Changing one package scales much better
than changing all other packages.
In addition, the completely unnecessary changes to dependent packages can
cause regressions such as:
https://bugzilla.redhat.com/show_bug.cgi?id=1479146
Kevin Kofler