The package is of the ( gnome+-2.2.1.tar.gz ) form.
Despite the hype you hear regarding the compiling of source code, you do not have to compile source to perform installation. Personally I compile source code only in the following cases
- When no RPM packages can be found (extremely rare case)
- When someone puts a gun on my head (This has not happened till date)
The reply below was sent to a newbie by Rick Moen (editor of linuxgazette.net) regarding the installation process of Xine. Hopefully, you will find it useful too.
Start quote
"
Let's review the ways to install new software into a Linux distribution such as Red Hat 9. First, you have the binary packages included on your distribution's CD-ROMs. Absent a compelling reason to the contrary, that should be the first place you look, because they're guaranteed compatible with your system, cryptographically signed by fairly trustworthy people, and are made easy to install. In this case, very likely you already checked, and found that Xine isn't included in your distribution.
Second, there are third-party repositories of software precompiled and packaged (by sundry individuals) for your particular distribution. E.g., the http://freshrpms.net/ repository has collections for all major distributions (and specifically for their individual releases) that use the RPM package format. Warning: Be careful about which collection at that site you draw from. Don't install an RPM designed for Mandrake, SuSE, Conectiva, TurboLinux, etc. -- just ones for Red Hat. (Yes, you can sometimes get away with those others, but don't try.) Don't try to install an RPM compiled for the DEC Alpha or PowerPC processor, given that you're running RH9 for x86. It's even best to stick to packages intended specifically for RH9, rather than for RH8/7.x, Fedora Core, etc.
Third, for a while longer, you can get package _updates_ from Red Hat via its "up2date" program, pulling packages from the Red Hat Network updating service. This is a very worthwhile facility,
Fourth, you can use tools to acquire and install packages from repositories such as FreshRPMs smoothly and automatically, taking care of "dependencies" (required packages needed to make the desired package work), using package-handling tools such as yum and Conectiva's port of apt-get to RPM.
Last, there are of course source-code tarballs (.tar.gz archives), which you can with varying amounts of effort and frustration compile and install. Note that unless you _also_ master the arcane art of making your own RPM archives from source (writing the "spec" file contained therein, which controls the RPM build process), your package-management system won't be aware of the software's presence -- a disadvantage. Compiling from source will therefore be usually a last resort relative to the other options, for any properly lazy sysadmin.
Therefore, I recommend that you start at http://freshrpms.net/, the FreshRPMs site. It has everything you need to get started.
"
End quote -- / \__ ( @\___ Raj Shekhar / O My home : http://geocities.com/lunatech3007/ / (_____/ My blog : http://lunatech.journalspace.com/ /_____/ U
_______________________________________________ ilugd mailinglist -- [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/[EMAIL PROTECTED]/
