The developer packages are required if you need to build stuff from source. If you're just installing RPMs and don't program, you don't need them (for the most part)
They contain stuff like headers and docs about the libraries and programs. I would normally install the dev packages for all libraries that I install, because I am a coder and it saves headaches when configure can't find a file it needs while building from a tarball.
Quote:
Originally posted by Agent_Embryo Usually you just
* download the tarball to a suitable directory,
* do: "tar zxvf filename.tgz" (if it's gzipped)
* go into the directory where the source was extracted
* type "./configure" this runs a script that configures the source for your system
* once finished type "make"
* and then when that's finished you can do "make install"
This is a quick and dirty method. I'm sure there are better ways but this has worked for me. Good Luck. |
While this does work, I feel I should point a bit out about some points that you've missed.
to do "make install" you need to be root.
The configure script also takes command line arguments, so you select what features of the software you want to build. Do "./configure --help" for more info. The most used option is the --prefix= one. This says where to install the program to. Normally this defaults to /usr/local which is ok for some things, but others you need to set prefix to either /usr or even / depending on the program or library. Especially if you're upgrading an older one as /usr/local isn't always in everyones path, and the guidelines are a bit fuzzy as to why its there.