Re: gcc 3.2 transition in unstable
On Mon, Jan 06, 2003 at 06:54:20PM +0000, Eduardo Pérez Ureta wrote:
> If upstream changed sonames in every API/ABI change.
Upstream has no control whatsoever about ABI changes caused by a new
compiler. Upstream does not need to change the soname in this case.
> And Debian changed sonames in the gcc-3.2 transition there shouldn't be
> any problem.
There is. Incompability with the LSB is worse than incompability with
prior Debian versions. (Otherwise we shouldn't have made the FHS