Re: RPM problem: How do I properly update glibc?

[Graham Campbell <gc1111 optonline net>]

On Tue, 2003-09-02 at 13:49, Chuck Campbell wrote:
> >On Fri, Aug 29, 2003 at 11:59:21AM -0700, Rick Stevens wrote:
> >
> <snip>
> > 
> > It shouldn't break anything except leave crumbs in your rpm database
> > that say you have the previous version installed also.  The "-ivh" would
> > work if you DIDN'T have a previous version but the dependencies are
> > circular (as they are with glibc...unfortunately).  I tend to agree with
> > you, however.  The instructions should read "rpm -Uvh" (install and
> > delete previous version).
> 
> Hopefully last question on the way to perfect clarity :-)
> 
> If I have messed up and installed an i386 version of package-X, then followed
> by installing the i686 version of package-X are they both there, or did
> the second install actually overwrite the binary executable image?
> 
> I suspect the overwrite scenario, so I assume the best thing to do is to 
> remove the two packages completely via rpm commands to clean up the database,
> and then reinstall the i686 version.
> 
> In the case of glibc, I don't want to remove the only current version from
> the last (i686) install, so how do I clean up the rpmdatabase?
> 
> thanks,
> -chuck

Sounds like you have not yet found the -l option for "rpm -q". It tells
you what files were installed. This can also be applied to an rpm
package file prior to install to see what files will be written (but
this needs the -p option)

I don't know about glibc in particular, but most of the important
libraries handle versioning. This is typically with version numbers
embedded in directory or file names and symbolic links to pick out the
correct versions.
-- 
Graham Campbell <gc1111 optonline net>