Quarternari wrote:Files from SRPMs are like downloading the source code tar files from apache/php/mysql?
Is there something I have to do other than ./configure and /make?
That is correct - they are source, but you don't use ./configure and make with these. Instead, SRPMS are used to generate RPMs for your system. They're "safer" than using standard builds, since the resultant RPM registers itself in your system for Add/Remove Software. Also - they include all the necessary patches and build "tweaks" for your OS.
SRPMs are usually processor independent. Generally, they will have the term "noarch" - no architecture - in the SRPMs title. It's easiest to use the SRPMs from the base distro - when I build Firefox, I use the CentOS SRPMs, since YDL is a translation of CentOS. You might need something newer though.
Building SRPMS isn't too difficult - you create a specific series of subfolders on your hard disc in a parent folder. I use a parent folder in my home directory called
rpm for this, then you manually create the subfolders - in all caps - called
BUILD,
RPMS,
SOURCES,
SPECS,
SRPMS underneath rpm.
After that, create a file called
.rpmmacros in your home directory (i.e.
nano ~/.rpmmacros) that tells RPM where to find your build tree. Mine looks like this:
- Code: Select all
%_topdir /home/paulp/rpm
Then, download the SRPM wherever you like, and build it with this command:
setarch ppc32 rpmbuild --ppc --rebuild foo.src.rpmWhere
foo.src.rpm is the name of the SRPM you downloaded.
We've found that you need the setarch ppc32 and --ppc arguments to correctly build for PowerPC.
After it finishes, you can just install it with
rpm -ivh newrpm.rpmwhere
newrpm.rpm is the resultant name of the RPM that is created.
If you need to upgrade an existing RPM, use the
rpm -Uvh newrpm.rpm command
You will need to be root user to install/upgrade the RPM. (i.e. use the
su command to switch to root user before issuing the rpm -Uvh.)
Cheers,
Paul