On Apr 12, 2007, at 07:56, Tom Malia wrote:
> 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?
Use the script svncopy.pl to make your tags (instead of running "svn
cp" yourself). svncopy will insert the -r argument in your externals
for you.
http://svn.collab.net/repos/svn/trunk/contrib/client-side/svncopy/
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 00:48:21 2007