It is not a big issue if SVN doesn't support taking a snap including external modules in nature.
A script below should work:
(1) get the external property
(2) Modify the property of externals with the tag. eg: http://test/lib1 to http//test/lib1/tags/rel_1
(3) svn copy the root module and external module to the corresponding directory based on the project layout.
all the modules then will have the same TAG.
(4) revert the property of externals
Now: svn co tagged_revision_path should check out the tagged copy for all modules directly.
The only rule is that all people using the SVN should put the tagged version to the specified place and they should
always use the script to TAG/Branch.
I am not sure whether it is a good way to work around. I am a newbie to Subversion.
Maybe I need to understand more about Subersion. The way SVN works is quite different from CVS.
regards,
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Thursday, April 17, 2003 21:16
To: Yanghui Bian
Cc: kfogel@collab.net; Justin Erenkrantz; Tim Moloney; dev@subversion.tigris.org
Subject: Re: Thoughts on user issues and how to attract the CVS user base...
"Yanghui Bian" <ybi@vitesse.com> writes:
> Both "svn update" and "svn checkout" work perfectly. SVN
> updates/checkouts the external modules.
>
> When I run "svn status", it only give the status of the root module.
It is a known bug that svn:externals do not work with 'svn status' or
'svn commit'. It's an unfinished feature at the moment.
> A more complicated issue is about the TAG/Branch. If I make a tag on
> the root module, What should SVN do to the external modules? Will
> it be difficult for Subversion to checkout the snap with both root
> and external modules of the tagged revision?
If you make a tag or branch, the newly copied directory will still
have the same svn:externals property, so it will continue to check out
the exact same externals.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 19 10:53:21 2003