A chroot environment to RPM Development Environment is another installation of Linux either on a seperate partition (recommended) or just installed into a specific directory

Another installation of Linux?? Are you serious??

Short Answer... Yes!  In order to build most RPM packages certain prerequisites have to be satisifed (or all your builds will fail, of course).  By having a seperate chroot environment builds can be performed without the danger of your build server becoming accidently tainted by wild builds.

I won't get into the steps involved in the installation of Linux as this is way beyond the scope of this document.  Given the fact that you are interested in installing this software, you should have this expertise.

When creating users for the front-end a chroot directory can be specified to allow for a seperate chroot environment for each user in the system.

Back to our favorite text editor for some configuration of the RPM Development Environment build daemon.  Adjust the following line to match the location of the common-modules on your build server.

use lib '/path/to/common-modules-1.0/'; 

Now for the quirky part.  Keep scrolling down...  past the You do not need to edit anything beyond this point comment.  I know, I know; I told you this part was quirky (this will be fixed up in the next release).  At line 42 you will see the following:

################################
# setup constants
################################

Edit the constants found below this line to match your system.

And that's it.  You should now be ready to start using your build daemon.