John Goerzen <jgoerzen@complete.org> writes:
> cmpilato@collab.net writes:
>
> > One caveat: don't expect your second repository to be a true copy of
> > your first. The repository stores all kinds of interesting bits of
> > data about how files and dirs have been copied and moved around, and
> > almost none of that is exposed via the RA interfaces. You should be
>
> Hrmm, that will likely be a fatal flaw then. Is that exposed at the
> repos layer or would I have to go down to the fs?
>
> Though, isn't the svn command-line client able to access that
> information? For instance, a svn log -v will show where something was
> copied from, and it obviously knows about adds and deletes.
Yeah, I guess you could try to use that.
I apologize, John, but I have to really need to bail out of trying to
help you further on this. I can't seem to convince you that you're
killing yourself needlessly. I mean, if your itching to do some
Python, you'd be better off just writing a simple Python server that
pipes 'svnadmin dump' output across a socket, and a client that pipes
that junk through 'svnadmin load'. But the RA bindings have had
practically no attention given them, and the functionality they would
offer is far too abstract to earn a higher priority than getting the
svn_client, svn_wc, svn_repos, and svn_fs bindings up to speed.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 2 18:11:03 2003