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

Tags/release-version and externals, best practices?

From: Tom Malia <tommalia_at_ttdsinc.com>
Date: 2007-04-12 14:56:19 CEST

I'm sure this has been asked and answered before, so I hope people don't
mind hearing this question again:

 

I've currently got a situation where I have several projects that are using
some shared code. I've got it setup such that the shared code is in its'
own folders within the repository and the projects that use that shared code
are using externals to include the shared code when it's checked out to the
working directory.

 

For trunk and branch development, this is working quite well for me because
each project is getting the "latest and greatest" versions of the shared
code and the programmer doesn't have to perform multiple check outs. they
checkout one project directory and get everything they need.

 

My question is, when I want to create a "snapshot" of all the source code
for a particular release of a project, what's the best way to do this given
the use of externals? If I just create a named Tag folder in my repository
for the release, then copy the trunk (or branch whatever the case may be)
for the project to that Tag, I assume I'm copying the externals links which
will still be pulling "HEAD" for the referenced code if I ever go back and
need to see the code for that particular release in the future. Is this
correct? If so, then obviously this isn't what I want. When I pull the
code for that Tag, I want to get exactly what was used to produce that
particular release. What's the best way to do this? Do I need to alter the
externals in the Tag? If so, what's the best way to do that?

 

Thanks in advance,

Tom Malia
Received on Thu Apr 12 14:57:10 2007

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