Hendrik Sattler <p...@hendrik-sattler.de> writes: > Am 18. Juni 2015 03:54:56 MESZ, schrieb Russ Allbery <r...@debian.org>:
>> Shared library symbol versioning makes the problem go away. Package >> dependencies try to solve the problem at the wrong level. > The problem is rather that the package dependency system doesn't look at > specific package dependency trees to find conflict between liblow1 and > liblow2. Instead it always does this globally. That problem is solvable. You missed the part of my message (which you snipped) where I specifically dealt with this. You cannot make liblow1 and liblow2 conflict without causing tons of other problems, such as preventing partial upgrades and making upgrade solutions infeasible. We want to support coinstallation of different SONAMEs of shared libraries and partial upgrades. These are major, important features for both our users and for our release and library transition process. > But you just but the burden on upstreams again. We can add symbol versioning in the Debian packaging even if it's not done upstream. We do that already for some libraries. It's obviously better to do it upstream, though, so that different distributions use the same versioning. It sounds like you're upset about my conclusion for some reason. You're certainly entitled to be upset, but your upsetness is not persuasive to anyone other than you. If you want to effectively argue with conclusion, you're going to have to address my rather extended explanation for why this is the best solution. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fv5py680....@hope.eyrie.org
