Duncan Murdoch wrote:
>
> No idea if this is practical, but how about something along these lines:
> subversion allows you to mix repositories in a checkout (see "Externals
> Definitions" in the book). So why not keep the big binary file in one
> repository, the source in another, and periodically wipe out the binary
> repository and start over? Presumably you'd commit a current version
> somewhere else whenever you did that. You'd lose all the commit
> comments (unless you print a log, and commit that too...).
>
> That is:
>
> On a daily basis your remote workers would work with the main source
> code and the temporary binary. All changes would be recorded and
> reversible.
>
> Whenever you want to set a milestone, you take the binary repository
> offline, commit a copy of the head and the log to some other place,
> recreate the binary repository and check the binary file into it.
>
> Hopefully someone with more experience in this than me will comment...
That's a good idea.
The only issue is that is the "busy" binary repository is cleared and
then has the large file added (so it's back at revision 1) all the
clients with svn:externals pointing to the busy repository will need to
delete the external subdirectory and then re-update. But the Subversion
client should warn you that something is affoot, like this:
svn: Reference to non-existent revision 254 in filesystem
'/Users/blair/tmp/repos/db'
Regards,
Blair
--
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion and Orca training and consulting
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 19 19:53:21 2005