File Explorer

1/*! \page multiplebuilds Multiple build areas2 3It is possible to run several RPM builds on the same machine using4separate RPM databases.  On my build machine I have several build5areas which all run builds at the same time.  The builds do not6interfere with each other.  Each build behaves as if it was running on7its own machine and no build area knows about the RPM database which8actually configures the machine.9 10First, setup a "topdir" in a prefix other then where RPM is11installed.  You will need to make the directories.  They need to be12writable by the account which will do the building, typically they13are owned by the buildmaster account and set to permissions14755.15 16\verbatim17        BUILD RPMS SOURCES SPECS SRPMS18\endverbatim19 20Next, you will need to decide where the database files live. I suggest21putting them in a separate directory under "topdir".  I call my22directory DB and it has the same owner and permissions as the other23directories.24 25Each separate build area needs a rpmrc and macro configuration file. This26will need to specify the new topdir and dbpath.  If you will be building27the same packages in different work areas you will also need to specify a28tmppath into the topdir.  I suggest either making tmppath be the same as29the BUILD directory or adding another directory called BUILDROOT for it30in the topdir.31 32Keeping track of the correct rpmrc for each build area can be33difficult.  To make my life easier I make a small shell script with the34topdir hard coded inside:35 36\verbatim37        #!/bin/sh38        /bin/rpm --rcfile /topdir/rpmrc "$@"39        exit $?40\endverbatim41 42I call the shell script rpm and it lives in the topdir.  Each time I43wish to use a particular build area I just ensure that the build area44is first in my path so that when I run "rpm" I get the regular rpm45binary but I am using the local build areas rpmrc.46 47*/48