John Belmonte <john@neggie.net> writes:
> I wish there was an "svnlook export", which would create a snapshot of
> a repository tree as it looks in a transaction. My use case is a
> pre-commit hook which verifies that the build is not broken.
>
> I've tried the following schemes to fill in this missing
> functionality, but each turns out rather ugly:
>
> * do an "svn export" and apply the transaction's "svnlook diff"
> to it. This doesn't cover changes to file permission
> (e.g. executable) or deleted directories. Working with subtrees in
> the repo is tricky-- I needed to use filterdiff (since "svnlook diff"
> doesn't accept a repo-local path) and calculate appropriate strip
> value for the patch command.
>
> * "svnlook cat" each file listed in "svnlook tree". Slow, and
> file permissions need to be handled manually.
>
> Also useful would be a "svnlook replay" which would replay a
> transaction into an existing working copy. Then I would: 1) maintain
> a pristine working copy in post-commit; 2) in pre-commit, replay the
> transaction into a clone of that working copy, check the build, and
> then destroy the clone.
There's no need to limit it to svnlook -- in general, I think, there
are a lot of interesting things we could do if the client could access
uncommitted txns in the repository.
That's a huge discussion/design effort, of course. However, I would
not object to starting it with something simple, such as the ability
to export (not check out) a transaction tree. Your call :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 20:03:41 2005