Comment # 8 on bug 1183960 from Cristian Rodr���guez

(In reply to Michael Matz from comment #6)
> An even more aggressive solution would be to stop having the pcre2-posix
> library at all.  Sources that consciously want the pcre2 variant of the
> POSIX regex facility can include pcre2posix.h without other changes in their
> sources and link
> against libpcre2 (without -posix).  And sources who do not consciously want
> pcre2
> under the POSIX names wouldn't link against libpcre2-posix anyway.  So
> providing
> libpcre2-posix at all seems to be a mere rope waiting to be hanged by.
> 
> But if the above is deemed too aggressive, then yeah, at least moving it to
> a separate package, not pulled in by mere chance, and making sure that no
> libraries
> we provide link against it, would be a solution as well.  So, thanks for
> doing
> that :-)  (I came from the gdb side via ncurses to look at this, and my
> initial reaction was: ncurses linking against pcre2-posix?  ugh, disaster in
> waiting :) )


I also played now with the possibility of also making the confliciting symbol
names compat symbols for old binaries only,.. found no way of doing this
without breaking the ABI anyway if the current library which is installed on
user's systems already lacks of existing versioning.

1 . Adding versioning == ABI break
2. plainly removing old symbols == ABI break
3. making pcre-posix old regcomp and friends symbols compat symbols goto 1.
4. using linker --default-symver uglier and goto 1
5. changing the library soname and fixing it correctly defeats all the point of
this excercise which is that I only care of old binaries linked rightly or not
to this library, the newely built ones do not really matter.

Do you know any other option ? afaik and extensive googling was unsucessful.