Bug#386228: libgcj7-0 (and by extension libgcj7) packaged such that conflicts are inevitable

[Don Armstrong <don@donarmstrong.com>]

On Sun, 24 Sep 2006, Matthias Klose wrote:

> Don Armstrong writes:
> > It could be that it not being in libgcj7 was a bug, and the placement
> > of libgjsmalsa.so.0 was a bug as well... but at the next soname bump
> > adding unofficial sonames to the shared libraries in /usr/lib/gcj-4.1
> > would be a good idea to ease transitions.
> 
> shared objects in /usr/lib/gcj-4.1 don't have a versioned soname
> anymore. gcj-4.2 uses /usr/lib/gcj-4.2.

Right; I believe that them being non-versioned is suboptimal, as it
leads to transition issues with anything that links against libgcj.
(The way it is now, we only get half the advantage of sonames on
libgcj.)

Changing this may be difficult, and it probably requires coordination
with upstream, but it seems clear that it's the right way to go. [Just
for those following along, with the conflicts everything that links
against libgcj has to be rebuilt before you can install (without
removing un-rebuilt stuff) anything that links against the new
libgcj.]


Don Armstrong

-- 
Tell me something interesting about yourself.
Lie if you have to.
 -- hugh macleod http://www.gapingvoid.com/archives/batch20.php

http://www.donarmstrong.com              http://rzlab.ucr.edu