Re: transition from 2.9 to 2.10 goes pretty smooth

[Justin Mattock <justinmattock at gmail dot com>]

On Mon, Jun 22, 2009 at 7:26 PM, Carlos O'Donell<carlos@systemhalted.org> wrote:
> On Mon, Jun 22, 2009 at 12:05 PM, Justin Mattock<justinmattock@gmail.com> wrote:
>> So the best way is to use a livecd
>> mount the partition, compile
>> and install libc to it's appropriate
>> destination.
>
> Yes.
>
>> Now uninstalling an old version of libc
>> I would simple just manually delete the old .so's
>> that are just sitting there?
>> Header files can probably
>> stay there(or delete them, and reinstall)
>
> No, it's more complicated than this. You should undo everything that
> the install does, fixing symlinks from libc.so to the old libc etc.
>

I guess the best approach would be to install libc
into a made up /dir (to see what it installs)
then go from there.(but probably better to leave the system as is)

>> What about things like(for example)
>> If I compiled some app with
>> libc 2.9, and them updated libc
>> to 2.10 and then delete 2.9
>> will that app still work, or does it
>> need to be recompiled with 2.10?
>> (so the app doesn't segfault)
>
> Applications compiled against an old version of libc will work with a
> new version of libc, this concept is called backwards compatibility,
> and glibc is backwards compatible (to a point).
>
> Cheers,
> Carlos.
>

ahh.. (being a newbie) I never
really knew what backwards compatibility
was.
Thanks for the info.

-- 
Justin P. Mattock