RFC: ABI break
Robert Millan
rmh at aybabtu.com
Fri Dec 23 16:00:37 UTC 2005
On Fri, Dec 23, 2005 at 04:20:02PM +0100, Petr Salinger wrote:
> >Petr's NOTES file indicates we'll have to change libc ABI due to (at least)
> >changes in struct statfs.
>
> We don't have to ;-) We can still use old struct statfs and change
> at any time later.
>
> It might be also possible join changing struct statfs with moving
> port to ftp.debian.org, but without soname bump.
>
> - change struct, add old compat functions at GLIBC_2_3 using ostatfs.
> new functions will get version GLIBC_2.3.5 or GLIBC_2.3.6
>
> - start rebuilding all packages and uploading them to ftp.debian.org
>
> Old aplication will use old functions from glibc,
> rebuilded new functions. The problem may arise only, when struct statfs
> is passed between old app and new app. I expect this will be uncommon,
> and only last a few weeks before all packages are rebuilt.
Ah, I see. Then the only remaining question (I think) is when do we switch to
the definitive soname 1, and wether we coordinate this with upstream.
I think upstream CVS has soname 1, so it'll be easier to keep it this way untill
we switch.
--
Robert Millan
More information about the Glibc-bsd-devel
mailing list