John Goerzen <jgoerzen@complete.org> writes:
> cmpilato@collab.net writes:
>
> > Well, it really depends on what you are wanting to *do* with the RA
> > bindings. Obviously, if you use the svn_client bindings, then you're
> > going to be limited to the types of operations exposed by that API.
> >
> > If you give me an example of what you're trying to do, I might be of
> > more assistance.
>
> OK, well first let me say that I haven't dabbled with the SVN API much
> yet. Just some simple things. This is going to be a learning
> experience for me, and I'm using Python.
Okey dokey.
> I have a need to take a complete backup of a remote repository *,
> and this seems like a good way. Plus it's a good way for me to learn
> about the Subversion API.
Hm. We use hot-backup.py + rsync to do the same, but that's if
irrelevant if your goal is to the learn the API.
The problem you're going to run into is that we don't *have* an API
for addressing the entire repository via a remote machine.
> As far as algorithm goes, my idea is to connect to each repository and
> get the latest revision number. Any revision that's not yet in the
> destination repository gets copied over, hopefully with per-revision
> properties (like svn:date) intact. I'm not planning any kind of
> bidirectional sync, since I think that's not at all appropriate.
What do you mean by "copying the revision over"?
I have a sneaking suspicion that the number of brick walls you are
about to encounter is akin to, oh, a cross-section of post-Fire
Chicago.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 2 16:20:16 2003