On Wed, Sep 25, 2024 at 9:46 PM Bernd Schubert <bernd.schub...@fastmail.fm> wrote: > I would like to ask how painful is a library (libfuse) .so for a > distribution? In what sense? Upstream ABI breakages don't help, I wait for 3.17 at least if that helps - not upgrading it to middle versions.
> As you can see here https://github.com/libfuse/libfuse/pull/1038 > there are some arguments not to do so. > The pull request above explains why and adds even more breakage, > when we already have chance for that. But it would be good to > know how much trouble it is for a distribution. Debian doesn't recompile dependent packages for new releases. Doing library transitions (due to new soname) is an everyday thing for us. The workflow is documented [1], I will not repeat it here. There are forty-two dependent packages that need to be rebuilt for such a case, not a big number. I'm open to schedule the transition if upstream changes the soname. Regards, Laszlo/GCS [1] https://wiki.debian.org/Teams/ReleaseTeam/Transitions
