Subversion and SPEC

Hi,

There is a free subversion service here in Taiwan found at 
http://opensvn.csie.org/ where you can register any project using a 
quite minimal registeration interface.

I'm beginning to administer my repository in subversion here: 
http://opensvn.csie.org/pyvault/.  The structure uses somewhat of the 
suggested layout from the svn book.

The /trunk directory will contain the latest generic spec files that 
should be buildable on the most wide-range of rpm platforms.

/branches will contain platform specific changes to the trunk to enable 
building for the platform.  It will contain directories using tag names 
from mach in the following form (architectures are dropped since the 
spec should be generic enough for the differences):

/branches/redhat-9
/branches/redhat-73
/branches/fedora-1
/branches/suse-82
/branches/mandrake-9
etc.

One prime example for needing this type of structure is the db4 
dependency on later versions of Python.  One .spec won't handle all the 
different scenarios between the distros--cleanly anyway. It's true %if 
and friends can be used here.

So, repo development will be like:

1. Select platform branch and merge from trunk.
2. Edit spec files.
3. Mach build the rpms.
4. Checkin specs.
5. Merge to /trunk for generic fixes, applicable to all branches, if 
needed.

BTW, most of the spec files in the above SVN are from pypackage.org 
built by Stefane Fermigier. I need to make them more generic, so I can 
do a "python2.3" prefix for platforms that already have an older python 
(rh73, rh9, fc1, etc.).

Anyway, let me know what you think...

take care,
-- 
-jeff