# $Id: README,v 4.2 2010/12/30 17:42:00 ksb Exp $

After you have a directory in sync (with msync) you can build automation to
extract the code (at a symbolic revision) into a temporary directory, build
a tar-ball, then a source RPM, then a binary RPM.  This automates feeding a
cluster of Linux (or Solaris) host via a pull system with apt or yum.

The packages built by this are called "level2's" in honor of the five layer
model term for this type of bundle.  We leav3e the apostrophe out because
that would be rude.

Note that this operation has an inverse which restores the master source
from the compressed tar archive.  That allows your subscribers to "down
stream" your code to fit their local site policy.

If you are looking to package up more than a single product you need a level3
package.

--
ksb, Dec 2010