Hi,
K, I want to upgrade to KDE-3.2.2 so I can us kopete (I have 3.1.something and it constantly crashes). Now, I am running RH9, and I have to upgrade various things to do this completely. Right now, I need to get qt-3.3.2 on there (I know that's not required, but I'd like to go to the latest if I am going to upgrade), but I can't install that because redhat-artwork-0.73-1 needs qt-3.1. So I figured I'd upgrade redhat-artwork to 0.96, but to build the rpm I need qt-devel.3.3.0 and kdebase-devel.3.2.0, which is annoying because that is what I am trying to upgrade to and the other dependencies won't let me do that. So, I am stuck in a circle here, and it is quite annoying. I am wanting to optimize all of the upgrade for my system, so I don't want to use prepacked rpms. Any suggestions on getting around all of this would be greatly appreciated!

TIA!
Mike.

so you want to compile qt, redhat artwork, and kde?

install the base dependencies, then, which would be qt-devel and kde-base devel, and work from there (the development packages should come in the sources for the programs/libs themselves and are usually automatically installed if compiled from source)

so install qt, then get the kde_base rpm, install redhatartwork, then compile kde which will overwrite the kde_base rpm (granted it is installed to the same $prefix)

the problem is, I can't install qt-devel without installing qt-3.3.2, and I can't install qt-3.3.2 because it would replace qt-3.1.1 which is needed by redhat-artwork-0.7x but I can't upgrade redhat-artwork to 0.96 because it requires qt-devel.3.3.2 and kdebase-3.2.2. See my dilemna? Any ideas on how I could figure out if qt-3.3.2 will provide the dependencies for redhat-artwork?

Thanks,
Mike.

so, you will temporarily break redhat_artwork... should it matter if it will get upgraded anyway?

there was a sticky post in this forum somwhere, and says that when you have circular dependencies, you can install the circular dependent rpm's with one command
rpm -Uvh package1.rpm package2.rpm

I don't mind breaking redhat-artwork temporarily, but I wasn't sure what it was for or if it was critical. I have gotten around the dependencies thing before with installing everything at once like you suggested, but the problem is I am building from SRPMS and they are requiring certain things also, so, if I can't get around those dependencies to build the packages, I am in trouble. I am confusing myself here, sorry if this doesn't make any sense. However, I could maybe install the prepackaged rpms just to get by the dependencies thing, and then rebuild the same packages to my system. Thanks for your help! When I get a chance I'll give it another shot and let you know how it goes.

Mike.

Are you using the "gui based " install ?

I went thru the same problem .. to install 3.2.2 you need
redhat artwork, artwork .. base and lib .. and yes .. you need qt 3.3 or what ever is newest


the way to do it is to use the shell... the gui based tool is screwed up, it only installs one package at a time
and is unable to handle multiple .. so multiple dependencies become cirucular.

Install qt (it should install by itself ) by doing
rpm -ivh qt* .. or rpm -Uvh qt*

others you should put them on the same commmand line .. i.e.

rpm -Uvh kdebase* kdelib* redhatart* ..

it will install them

(make sure you don't have a lot of other stuff in the directory where you run the commmand .. and of course
you have to be root)

the problem is I am building from SRPMS and they have requirments that I can't meet because of my system limitations. I can't simply do a rpm -ivh for example because I am dealing with SRPMS, so part of my problem is building the actually rpm's, I am struggling with that and my dependencies. Thanks for the replies!!

Mike.