Re: Planning for libidn shared library version transition

[Timo Röhling]

Hi Simon!

* Simon Josefsson <si...@josefsson.org> [2021-05-24 19:34]:

I want to upload a new upstream libidn release into Debian, but upstream

has done a shared library transition.

You should probably read the Release Team documentation [1] on library
transitions if you haven't done so already.

Is the first step on the transition to provide a libidn-dev package
experimental (and after the release, unstable) and make all reverse
build-dependencies use it?

Generally, it is a good idea to have a libidn-dev package instead of
libidn11-dev, so +1 on that. It will avoid sourceful uploads of
reverse-dependencies in the future.

However, I noticed that Debian ships with the successor library
libidn2 already, and its homepage says it provides a compatibility
layer for libidn. So wouldn't it be better to sunset libidn in favor
of the new version?

Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

signature.asc
Description: PGP signature