All,

   With Arch, it is useful to create tarballs from the svn tree for the 
different Trinity modules to prevent having to download the code each time you 
attempt a module build. When building in virtualbox, you can keep the svn source 
between build attempts so there is no need, but when building in an 'archroot', 
it starts with a fresh environment for each build with requires a full svn 
checkout with every build attempt. Baho has provided scripts that do this.

   I took the idea and just put together a standalone script that can be applied 
to any generic svn directory. In its simplest form you are just doing a:

   tar --exclude-vcs -czf mytarballname.tar.gz svn-module-dir/

   Which creates the tarball while removing all the 'version control system' 
(vcs) files (i.e. all the .svn dirs). What I've added to the basic tarball 
creation is the svnversion information so the script will automatically produce 
a tarball named:

   <trinityModName>-<svnversion>.tar.gz

and provide the md5sum information from the simple call of

mksvntgz.sh path/to/trinityModule [path/to/put/tarball]

(the default tarball output path is ~/tde/tgz

i.e. so you can just do:

mksvntgz.sh ~/tde/trinity/kdebase

which will create kdebase-1231922.tar.gz in ~/tde/tgz and write the md5sum 
information to ~/tde/md5sums.txt. It can easily be adapted to do the whole svn 
tree by putting the call in a for loop calling it once for each of the modules.

   Creating a link is /usr/local/bin can cut down typing. I use:

ln -s /path/to/mksvntgz.sh /usr/local/bin/mktgz

   Then it is just 'mktgz moduleName'

   Nothing special or magic about the script, but if anybody has the need to 
create tarballs from the svn source, this will save you a bit of time. Also, if 
you just want to cannibalize pieces of it, feel free. The script is:

http://www.3111skyline.com/dl/dt/trinity/arch/scr/mksvntgz.sh

-- 
David C. Rankin, J.D.,P.E.