Safe glibc replacing with a newer one
 

I want to completely replace old glibc with newer one. To do this more safely, I decided to put new glibc into /usr/local for a first time, build all core packages using it and then... change prefix for glibc to /usr, backup old binaries, libs and do a "make install" for each package and glibc itself.
It's a good practice?

"It's a good practice?"

You can make it work. But you will have to do a lot more work to install any packages with glibc in an unusual location. You probably will not be able to install any SuSE rpms and anything that you install in the future you will have to compile yourself and you will have to change the ./configure files to point to the new glibc location.

----------------------
Steve Stites

No, I just want to keep safe older glibc libraries before all "core" binaries, such as grep, find, ls will be compiled and installed. Then I want to remove older glibc at all and install new to common location, i.e. into /usr. I don't want to use any rpm's - my general goal is to build _all_ system from sources.

Sounds like madness to me. Why don't you just rebuild Linux From Scratch?

You're right :( Even don't know how such things are pull up in my brain :((

its simple, with linux your generally free to do whatever random thoughts come to your mind..unlike some other systems..! :jawa: