Alexander,
Thanks for your comments.
>
> If that approach does not suit you, you may want to, for example,
> only use svn:externals without explicit revision for the trunk (to
> keep up with the Widget_1 without additional hassle), but then you
> should always remember to add explicit revision information when you
> create tags/branches of your project.
It's that "you should always remember to..." phrase though that is at
the heart of the issue. I would think that one should be able to
recover an exact earlier state of the repository without the
repository having to rely on a user action of "you should always
remember to..."
> To accomplish this, you may
> create tag/branch not from the Repo Browser, but from a WC, in which
> you have added the explicit revisions for all svn:externals
> properties just for the sake of tagging/branching. This approach can
> be scripted/automated.
>
Does that scripting/automating tool exist today though? Just like
Tortoise provides a nice GUI to Subversion, some form of tool that
could go through a WC and lock down all the externals would be handy.
> K> or simply Zip the sources up and
> K> maintain that as another archive of what 'really' was there when the
> K> repo was at the level used in the release.
>
> People often start using version control tools exactly to get rid
> of such zipped source archives.
>
I agree, and don't want to rely on ZIP sources either but at least
they are providing a snapshot of what really existed at that moment in
time.
KJ
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1234361
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-26 20:05:09 CET