Self Compile VS RPMs
 

I'v just about get this RPM thing down, guess that is because everything I'v wanted is a *.rpm but when I download these files I see a .src.rpm as well come to find this is a source file so you can compile it yourself. Is this true:Pengy: If so how do I go about doing it? :confused: (It would be nice so I don't have to mess with dependencies)

i like using the binary rpms first, but if i cant, then i compile the sources. compiling varies depending on the program, but usually you go to the directory of the sources and type "make" (no quotes) witch usually works. you should look in the readme first, however.

i see your distro is redhat 9 so this is the command your looking for:
rpmbuild --rebuild nameofpackage.src.rpm
/usr/src/redhat/SOURCES is the default install directory for the source rpm.

Thanks DrOzz

RPM files are ok but you don't get any optimizations for your system--Pentium 4 don't do well with RPM files. Also some RPM files don't come with special files that other programs need. Compiling a program takes care of those problems assuming you read the documentation and read through the ./configure --help. Uninstalling RPM files are a pain in the ass. They always depend on other RPM files. For a compiled program, you just delete its directory and the symbolic to the program.

For the RPM dependences problems, you can install apt-get or urpmi.

I like using source code first. If it doesn't work, I guess I had to tweak the source code or download the RPM file. For my library files, I use RPM files because I don't have a choice with my distribution. If I installed Slackware or FreeBSD, I would be compiling the library files. Though after a four months of using LINUX, I'm still a :newbie: . Maybe in a few years, I'll install either Slackware or FreeBSD.