Ilyes Gouta wrote:
> Hi!
>
> I have a special use-case that I would like to have your opinion on
> and if it's doable or not using Subversion. So, here it is:
>
> I'd like to "clone" a public SVN repository and make the new
> repository accessible to my team. Each member of my team will have his
> working copy checked-out from the "cloned" repository, which is
> internal, and will check-in its code to it. I'd like also to
> periodically synchronize that repository with the public one to
> reflect the latest public changes. So, the "cloned" repository will
> act as a repo. as seen by my team members and as a "working-copy"
> from the public repository point of view.
>
> Is this doable using SVN?
Well, it sounds like you really need to use a Distributed VCS, and if
the upstream repo is SVN, use a plugin to your DVCS to mirror the SVN
repo. git-svn, bzr-svn and hg-svn should all do this quite well (git is
best here with full pull and push support, hg (mercurial) is fine for
pulling changes, and will improve soon with a GSoC student working on
enhancing the push-changes-upstream-from-hg-repo-to-svn-repo support).
However, all 3 have only so-so support on Windows, which may be a
problem for you (I'd say, in order, they go HG, BZR, GIT, from best to
worst Windows support).
Another option is SVK, a distributed VCS built on top of Subversion
(this will be the most seamless alternative I think - I think your repo
controlling dev or devs can manage the cloned repo using SVK commands,
but other devs just use it as a plain SVN repo, e.g. using TortoiseSVN
or similar).
See also:
http://svk.bestpractical.com/view/UsingSVKAsARepositoryMirroringSystem
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-12 16:19:16 CEST