On Nov 16, 2006, at 11:58, Mark Clements wrote:
> OK - I see how this works, but it's quite a bit of work to redo
> whenever the
> default setup changes. Not sure how often that will happen but it
> could be
> an issue. Is there maybe some way of doing this by playing with the
> relocate/switch statement? The currently proposed solutions are not
> currently simple enough for my purpose - I want to be able to have a
> 'default_repo' that gets tweaked and modified as required, and for my
> createrepo script to seed a new repository with revision 1 that
> matches the
> head of default_repo, with no user intervention required.
>
> If that is not possible, then I will probably get my script to
> manually
> construct the first revision in a temporary working copy, commit
> that and
> delete it. This would mean that any modifications would need to be
> made
> directly in my setup script rather than in a versioned repository,
> but this
> is probably the simplest solution if I can't automate the above.
Have you tried the "dump head revision / load" strategy someone
mentioned? I think it works and it's easy:
svnadmin create /path/to/newrepo
svnadmin dump -rHEAD /path/to/oldrepo \
| svnadmin load /path/to/newrepo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 00:28:29 2006