Bug#958905: Multiple versions of libocct cannot be installed

[Tobias Frost]

Source: opencascade
Followup-For: Bug #958905
Control: tags -1 upstream wontfix
Control: close -1

Hi Yuri,

Upstream unfortunatly does not properly manage SONAMES, so it is currently the
only way how opencascade can be managed in Debian: The library packages of
the different versions have the smae library name, so they cannot be 
co-installed.

We need the Breaks/Replace to ensure that the updates will happen, as the
different libraries versions are not binary compatible and we need to ensure the
right version.

OTOH, we won't have multiple opencascade versions anyway in Debian and the
library transistion ensures that all packages in Debian will use the same
version; at least in testing and stable releases.

I understand that there are usecases that would benefit from be able to
coninstall the libraries, but that should be done upstream first and then
done in the Debian packaging;

Closing this bug as wont-fix then.
(I recommend yout to filing this request upstream instead.)


-- 
tobi

Bug#958905: Multiple versions of libocct cannot be installed

[Yuri D'Elia]

Package: opencascade
Version: 7.3.3+dfsg1-2
Severity: minor

My understanding is that when choosing to include the version in the
package name of a library, is that so that we can allow for multiple
versions of the library to coexist on the same system.

However all libocct-* 7.4 libs break 7.3, which defeats the point
of major-minor version in the package name itself.

Would it be possible to avoid the Breaks or there's some underlying
issue?