[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Different ways to create tags -- is this OK?

From: Jennifer Kesterson <Jennifer.A.Kesterson_at_jpl.nasa.gov>
Date: 2006-02-09 00:51:04 CET

I have two questions about tagging for each delivery. First, a little

Our Subversion repository contains the following structure:

For each delivery, we create a new subdirectory "Bn.n" in /tags and put all
the subsystem tags in it. Each subsystem tag consists of a specific
revision of that subsystem's directory on the trunk. The /tags directory
then looks like this:

After all subsystem deliveries are complete and tagged, I create the main
system tag from a copy of the Bn.n directory. We do this because the
system tag consists of the subsystems actually delivered for that build,
not just a specific revision on the trunk. The /tags directory then looks
like this:

To build, I simply export the main system tag into the build directory.

I chose the above method of making the system tag because it is the fastest
(especially when using the GUI client) and it seems a sure way (via the
copy) to contain the exact contents of each subsystem tag already made.

Question #1: Is that a sure method of creating the system tag so that it
contains the same revisions used in the subsystem tags? We check the
contents of both and they appear identical. Another method described in
the book -- though a little more work -- is to extract each subsystem tag
into a work directory, then copy the work directory to create the new tag.

Question #2: Is there any problem with organizing our /tags directory with
subdirectories for each delivery?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 9 00:52:36 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.