-   Linux - Software (
-   -   upgrading packages (

paulr1984 03-23-2005 03:04 AM

upgrading packages
hi! I'm using fedora core 3 and I'm trying to upgrade some packages like atk. I was wondering how to properly upgrade packages. I don't want more than one version installed at the same time. I know that with rpm, you can just use the -U option. Does that remove the old version? What if it doesn't come as an rpm? Instead, you only have the source code. How do you upgrade then?

DaBlade 03-23-2005 03:27 AM

you gotta install arts first, kdelibs second, kdebase third and then the rest.
Here's an example of how you can install them, but this is in case u have devel packages of the old version installed:
rpm -Uvh --force --nodeps kdelibs-3.4.0-0.fc3.0.i386.rpm kdelibs-devel-3.4.0-0.fc3.0.i386.rpm

basically rpm -Uvh --force --nodeps is what you need. Remember, arts>kdelibs>kdebase>the rest. if accompanied by devel packages, install them too (only if u had devel packages for the old version)

__J 03-23-2005 04:45 AM

usually, if you get an rpm for your specific distro, it will install in the correct prefix upgrading the older package. from source, you could remove the old package and install the new, but this method has a couple drawbacks. The other way would be to build your source, create an rpm from your build, and install that. there are a few ways to do this, manually, scripts, there is a program called checkinstall that will build rpm's for you, etc.. The advantages of this method are since it's an rpm, upgrading/removing will be much easier and it also upgrades the rpm database, so if you are trying to install something that depends on what you installed from source, it will help with dependencies.

As a side note, --force and --nodeps shouldn't be used unless you have to. you can install any package with those switches, but unless the dependencies are actually on your system whatever you installed will not work correctly. I assume you want to upgrade atk to upgrade your gtk-2. It's usually a good idea when doing this from source, install these libs back to wherever they were installed by the system ( probably /usr/lib). And don't forget to read the README when you get to pango :D

dr_zayus69 03-23-2005 06:16 AM

i use YUM to install and upgrade my rpm packages. You can have it check to see if any available uprades are available and install those. I'd recommend getting comfortable with it. man yum in the terminal to learn more or google around.

paulr1984 03-23-2005 06:34 AM

I wanted to ask about upgrading in general. Atk was just a sample. Building my own rpm seems to be quite overwhelming considering my limited skills in linux. I think I will have to go with upgrading from source. Here are some things I would like to clarify:

- If the packages I want to upgrade are needed by some applications currently installed, can I simply remove them forcibly and install the newer version?
- After installation(make install), can I just delete the folder containing the source (and compiled stuff) since the necessary libraries are already installed in my system? In this case, how do I uninstall if I want to do so later on?
- If I installed it through source, I cannot do a 'rpm -q SomePackage' on it, right? How do I check if its installed or what version it is?

These are a lot of questions. Pardon my ignorance.

paulr1984 03-23-2005 07:35 AM

I checked yum and played with it for a while. But I noticed that it only looked at files in But the latest versions are in the home pages of the packages. I guess it seems absurd to think that I expected yum to check all those webpages.

__J 03-23-2005 03:42 PM

I believe you can change the repositories for yum so it finds different packages ( don't quote me on this, I haven't used an rpm distro for some time).

I strongly suggest you learn how to use rpm as well as build them from your source builds. If you remove the source directory, unless you install each package into it's own directory and manually alter all of the relevant paths, removal is going to be a pain and will take alot of time. check out checkinstall, it makes rpm's ( and debian and slackware packages too). If you build from source and make an rpm, it upgrades the rpm database so you can use the same commands on it just like any other rpm.

also, make sure you are upgrading for a good reason. In open source, software is released quite often but that doesn't necessarily mean you need to upgrade or that upgrading to a newer version will be beneficial. check and make sure it has something new that you want that isn't in your older version, or a security fix, etc...

All times are GMT -5. The time now is 04:03 PM.