1.6.0 RPM available for Redhat 6.2 available yet

Linas Vepstas linas@linas.org
Wed, 20 Jun 2001 12:12:17 -0500


On Wed, Jun 20, 2001 at 12:17:59PM -0400, Bill Nottingham was heard to remark:
> Linas Vepstas (linas@linas.org) said: 
> > > But programs compiled against glibc-2.1 *should* work with 2.2, right?
> > 
> > Yeah, but redhat picked a non-standard version of the compiler as well.
> > The way redhat dependencies work, you can't install the newer glibc
> > without also installing virtually the entire system.  Its pretty much an
> > all-or-nothing thing.  That's why they bumped the major version number.
> 
> Huh? There's nothing to prevent installing glibc-2.2 without upgrading
> the compiler.  You might need some compiler patches to *rebuild* glibc,
> though.

I guess I should look at email addresses first, before I post.

I had an rh62 system at home.  I wanted to install some new-improved
thingy from rawhide (which at that point was between rh70 and rh71).
But the dependency cascade was such that by the time I got done
installing, the system would have defacto become an rh70 system. 
This was a more traumatic change than I wanted to have.

(I still have a rh62 server. It will stay rh62 until its decommissioned.
It works, and the last thing I need is to spend time upgrading it.
A day to install .. another 3 days to make sure each damon still
works right.  A month of watching & waiting to make sure its really
stable, and dealing with the various instabilities as they invariably
do creep up. (e.g. log file formats that change, requireing
log-monitoring tools to be upgraded/reconfigured, etc.) Upgrades 
are fundamentally hard.)

--linas