Shared library version bump?

[Daniel Eischen]

On Sun, 21 May 2006, Julian Elischer wrote:

> Daniel Eischen wrote:
>
>> On Sun, 21 May 2006, Julian Elischer wrote:
>> 
>>> Hajimu UMEMOTO wrote:
>>> 
>>>> deischen> Go ahead.  Just realize though, that after 7.0 is released
>>>> deischen> you will have to support any ABI from then on without version
>>>> deischen> bumps (meaning, you have to keep shims for any old 7.0+ ABIs
>>>> deischen> in libc).
>>>> 
>>>> ume> Okay, I'll do.
>>>> 
>>> 
>>> I assume htat EVENTUALLY we will bump numbers again when something 
>>> sufficiently
>>> big needs to be done to the ABI.
>> 
>> 
>> Symbol versioning is suppose to allow one library to support different
>> ABIs, so the hope is that we will never have to bump libc's version
>> number.  If you change ABI, you still have to keep the old code around
>> (or some sort of compatability shims) in the library.
>> 
> yes but that could get too big  a drain on resources oftetr  while (trying ot 
> shim really old
> stuff into really new stuff.) It might eventually get to a point where it 
> would be good
> to cut and run..

You can never say never, but we need to better maintain our ABI.
I believe Solaris has had one only version of libc from day one
(Solaris, not the BSD-derived SunOS).

I can see bumping libc version number again if, for instance, we
were to move the resolver stuff into libresolv, or something
like that.

-- 
DE