Dne 11. 09. 20 v 9:48 Florian Weimer napsal(a):
* Tom Hughes via devel:
> On 11/09/2020 07:13, Ondrej Dubaj wrote:
>
>> There seemed to be no big reason for moving the libraries to the
>> main package in the past, so I consider f34 as a good candidate for
>> such a change. It would be great, if you share your opinions and
>> concerns for this topic.
> Tom Lane has explained the reason on the ticket, it's because the
> library is often dlopened by a client application instead of being
> linked to.
"often" is relative. I see this mentioned for following packages:
java-1.5.0-ibm-jdbc
java-1.6.0-sun-jdbc
java-1.5.0-bea-jdbc
Which probably shares common history and at least one of them admitted
the mistake [1] and started to use the versioned .so file.
So are there any other cases?
Yes, that is sufficient reason not to do the move. Third-party
applications will break.
And they should be fixed. I understand there is never the right time to
fix this, but if not now, then when?
Some people also really dislike installing
*-devel packages in production, so there might not be an easy fix for
them.
The library probably should not have a versioned soname in the first
place, with backwards compatibility achieved by different means. But
that does not matter now.
Thanks,
Florian
Vít
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=215777#c24