Re: gcc 3.2 transition in unstable
On Mon, 6 Jan 2003 21:14, Sebastian Rittau wrote:
> 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.
One thing we should probably keep in mind is that GCC is not the only C
compiler, and that Upstream may not even particularly like GCC.
I know a few programmers who would be happy to have a hissy fit about such
things rather than agree to a GNU forced change to any aspect of their
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page