[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [parisc-linux] gcc-3.3 configuration

> If yes, does the following approach work: Build a libstdc++5-3.3,
> conflicting with libstdc++5 (including libstdc++ with the same soname)
> and doing binary uploads for hppa for all libstdc++5 dependent
> packages? (The same could be done for m68k, but the compatibility
> argument doesn't hold as Debian seems to be the only m68k based
> distro).

Aside from the evilness of doing binNMUs of this magnitude, I doubt a
"transition" that doesn't change the SONAME will work. As soon as the
new libstdc++ is installed, every c++ app on the box will instantly
break. This means if anything happens e.g. to apt during the update, the
system will get into a very nasty state. I don't think this is worth it.

If we need to change the SONAME, then there's no binary compatibility

As willy mentioned in his other email, if other distros want binary
compatibility, they should follow what Debian is doing (on hppa), since
Debian was there first :-)

my 2 cents,
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports

Reply to: