[NTLUG:Discuss] Upgrade breaks things

[brian@pongonova.net]

On Fri, Apr 12, 2002 at 01:23:00PM -0500, Bobby Sanders wrote:
> 
> I had always assumed that libraries _were_ backwards compatible,
> i.e. if it works with lib.x.0.1 it should work with lib.x.0.2.  If
> /lib/modules/2.4.8-34.1mdk/modules.dep is backward compatible with
> /lib/modules/2.4.8-26mdk/modules.dep, perhaps a soft link would work?

Unfortunately, that's not the case, even with the most important
libraries.

For instance, glibc 2.1.x is not backwards-compatible with 2.0.x.
Sure, many of the interfaces are the same, but it's always the one
that changed that will bite you :)

If you are someone who religiously updates their system with the
latest RPMs/debs/<insert newfangled package buzzword here), and
religiously keeps up with the O/S updates, then the issue of backwards
compatibility is moot.  As someone just suggested,  Debian has a good
system of keeping updated with the most cutting-edge stuff -- this, of
course, is only helpful if you also don't mind continuously updating
applications on your system.  

I realize this isn't a solution to your problem...I just wanted to let
you know that what you're experiencing is a problem not unique to your
particular system.  It's a tradeoff you have to make: Cutting-edge
Linux most likely means cutting-edge apps...stable, older Linux most
likely means doing without certain updated apps.

  --Brian