[5405] in Release_7.7_team
Dev framework for modified RPMs
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jan 30 18:55:46 2006
Date: Mon, 30 Jan 2006 18:54:44 -0500
Message-Id: <200601302354.k0UNsiSK015046@egyptian-gods.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@MIT.EDU
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Spam-Flag: NO
Recently, I wrote about the need for a development discipline for
maintaining sources based on modified RPMs:
This mostly means a script for running "rpmbuild -bp" on an SRPM
and importing the result into a version control system.
The version control system could be the Athena CVS tree, or a new
Subversion repository for each package. I can think of arguments
for either.
Here are the arguments on each side. For CVS:
* Our existing CVS tree is already set up and we know how to use it.
* It keeps more of our sources in one place.
* Using Subversion would require using a tool like svn_load_dirs.pl
or svk to do the imports, since Subversion doesn't have a native
function for repeated imports. (svn_load_dirs is in the
Subversion contrib directory and is pretty straightforward,
though.)
For Subversion:
* I'd like to be piloting Subversion in more contexts, and this is a
low-risk way of doing so.
* Subversion may do a better job of keeping the diffs against the
vendor branch clean, due to quirks in CVS.
* This stuff will not be built by build-all.sh, so it arguably
doesn't belong in the main Athena tree.
I'm going to head down the Subversion road for now, but the resulting
script will likely be easy to convert to use CVS if we change course.
The bulk of the work writing the script will be figuring out the least
obtrusive way of converting an SRPM into an importable source tree.
