This is very similar to something I did using CM Synergy some years back. I
created a "Release" project (i.e. view into the repository), added to it the
projects that contained the code/products/etc as subprojects, and ran a
makefile that understood the various directory structures (or at least how
to call other makefiles) to package the contents for shipment. The
subprojects that contained code/products/etc included a 'base' package as
well as customer-specific 'custimization' packages that could be laid on top
of the base depending on the customer (replacing various base files). In
the last steps, the makefile created an InstallShield package and a
subsequent CD ISO image.
It sounds like the svn:externals route described in a previous message may
be a way to create such a set up.
-Brandon
On 3/30/06, James Courtier-Dutton <james.dutton@gmail.com> wrote:
>
> Hi,
>
> Thank you everyone for all the feedback. The solution we have choosen
> is a release script.
> This saves us having to tag any files, and is actually quite simple to
> manage.
> The script itself will be stored in the SVN.
> So, the process to build a release:
> checkout the release script.
> run the script.
> The script executes various svn checkout commands retrieving the
> correct versions of various repository directories into a tempory
> working directory tree.
> The script then does simple copy operations to copy the correct files
> into the correct customer release directories ready for writing to
> CD/DVD.
> Job done. :-)
>
> James
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
-B
Received on Thu Mar 30 19:53:26 2006