I am thinking of living on the bleeding edge and would like to upgrade
from the egcs packages that came with RH 6.1 to the pinstripe gcc, cpp,
qt-2.1.1, and glibc packages.  I am finding a lot of packages (new KDE
beta's) that require new qt, and new Qt packages require libstdc++-6.2-2
at least.

I have downloaded the following:

binutils-2.10.0.18-1.i386.rpm   glibc-profile-2.1.91-18.i386.rpm
cpp-2.96-46.i386.rpm            libstdc++-2.96-46.i386.rpm
gcc-2.96-46.i386.rpm            libstdc++-devel-2.96-46.i386.rpm
gcc-c++-2.96-46.i386.rpm        qt-2.1.1-14.i386.rpm
gcc-chill-2.96-46.i386.rpm      qt-GL-2.1.1-14.i386.rpm
gcc-g77-2.96-46.i386.rpm        qt-NSPlugin-2.1.1-14.i386.rpm
gcc-java-2.96-46.i386.rpm       qt-Xt-2.1.1-14.i386.rpm
gcc-objc-2.96-46.i386.rpm       qt-devel-2.1.1-14.i386.rpm
glibc-2.1.91-18.i686.rpm        
glibc-devel-2.1.91-18.i386.rpm

When I try rpm -Uvh *.rpm I get the following conflicts (samples only,
there are a lot more!):
....
        libdb.so.2 is needed by libglade-0.13-0_helix_1
        libdb.so.2 is needed by memprof-0.3.0-4_helix_3
        libdb.so.2 is needed by gnome-linuxconf-0.23-1
        libdb.so.2 is needed by gnorpm-0.9-10
....    
        libdb.so.2(GLIBC_2.0) is needed by python-1.5.2-7
        libdb.so.2(GLIBC_2.0) is needed by helix-update-0.5-1_helix_5
        libdb.so.2(GLIBC_2.0) is needed by pan-0.8.0-0_helix_1
        libdb.so.2(GLIBC_2.0) is needed by gnome-libs-1.2.1-0_helix_1   
....
        libdb.so.3 is needed by sendmail-8.9.3-15
        libdb.so.3 is needed by vim-X11-5.4-2
        libdb.so.3 is needed by vim-enhanced-5.4-2
        libdb.so.3 is needed by pam-0.72-20

....
        libstdc++-libc6.1-1.so.2 is needed by kdeadmin-1.1.2-3
        libstdc++-libc6.1-1.so.2 is needed by kdebase-1.1.2-10
        libstdc++-libc6.1-1.so.2 is needed by kdegraphics-1.1.2-2
        libstdc++-libc6.1-1.so.2 is needed by kdelibs-1.1.2-9
        libstdc++-libc6.1-1.so.2 is needed by kdemultimedia-1.1.2-3
        libstdc++-libc6.1-1.so.2 is needed by kdenetwork-1.1.2-4

Is there any way around this?  I'm not sure I am brave enough to install
with --nodeps, I'm afraid I will break something.

Is this something I could 'install' instead of 'upgrading'?  Other than
at a high level, I am not sure of the difference between upgrading an
RPM versus installing a newer version next to the old.

TIA

-- 
Tom Porter                                   [EMAIL PROTECTED]
--------------------------------------------------------------------
"On two occasions I have been asked [by members of Parliament], 
'Pray, Mr. Babbage, if you put into the machine wrong figures, will 
the right answers come out?'  I am not able rightly to apprehend the 
kind of confusion of ideas that could provoke such a question."



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to