https://bugzilla.suse.com/show_bug.cgi?id=1183960 https://bugzilla.suse.com/show_bug.cgi?id=1183960#c10 --- Comment #10 from Cristian Rodr�guez <crrodriguez@opensuse.org> --- (In reply to Michael Matz from comment #9)
(In reply to Cristian Rodr�guez from comment #8)
Do you know any other option ? afaik and extensive googling was unsucessful.
Merely providing a symbol version when there was none before shouldn't break existing uses (the referenced unversioned symbols will be satisfied by the lowest versioned one). But you can't remove the symbols in that way, that will always entail a soname bump.
But we can ask ourself if we ever want to be able to produce _new_ libs/binaries that link against libpcre2-posix (and use the POSIX symbol names). A way to do that would be to move the prefixed functions from that lib into libpcre2 itself: pcre2_regcomp, pcre2_regerror, pcre2_regfree, pcre2_regexec. Then provide a mostly empty libpcre2-posix.so.2 (for old libs/binaries, i.e. containing the POSIX names), but _not_ provide the libpcre2-posix.so symlink. In that way nothing within openSUSE could link edit new libs/binaries anymore that would run into this problem. Over time the existing binaries and libs at users system that still make use of libpcre2-posix will be gone, at which point we then also can remove the libpcre2-posix2 package.
(The reason for moving the functions is so that sources that make validly use of <pcre2posix.h> and hence reference pcre2_regcomp for instance can continue to be built, but they would need linking against libpcre2 proper, instead of against libpcre2-posix, which in that model isn't possible anymore).
Of course, moving the functions from one to the other lib should not be done without buy-in from upstream.
This sounds straightforward but .. all of this for.. I checked the debian archive.. there is ONE package using this library and it is probably by mistake. TW otoh currently has few dozen only because they were infected indirectly, once ncurses hits factory the list will shrink to a few or none. -- You are receiving this mail because: You are on the CC list for the bug.