Planning: Pydar2 rpm buildserver: Dries RPM Repository

Recent changes:

• New option in master config: checkmissingtagsperdistro. When this option is set, the master checks if the most recent version of each spec file has tags for each distro/arch combination in the database. This slows down the startup a lot and it shouldn't be needed with normal use.
• Fix: the slave now creates the cache dirs for yum if needed.

Short term:

• 23/5/2005: get the first pages about pydar2 online: done
• 25/5/2005: change buildroot so it checks for a yum config for a buildmachineid first: done
• 25/5/2005: basic document about installing the slave buildmachines: done
• Create templates for the yum configurations: only for fc done
• 26/5/2005: update the classdiagram and put it online: done
• create a basic document about the client: todo
• 28/5/2005: make sure the mails contain meaningfull stuff: done
• finish the spec file of pydar2 and build the rpms + put them online: not yet done..
• Basic version of autoqueueing: done
• RsyncYumBasedBuildRoot: first version done

Near future:

• finish MemoryStorage so it's possible to use pydar2 without a PostgreSQL database (and without much persistence data)

Also on todo but not highest priority:

• SmartBasedBuildRoot
• AptBasedBuildRoot

Low priority, but needed once nevertheless:

• Check if it is possible to make pydar2 agnostic about spec files and rpms. Would it be difficult to build other stuff like slackware packages for example?
• Create an selinux config for at least the master and the client. The slave is currently very insecure and uses sudo for certain tasks so slave buildmachines should at least not be publicaly accessible.