Transaction building with bindings, do I need a WC on disk

I've a couple question regarding what's generally possible that I think
some developers could probably answer pretty quickly.

If I'm using the Python (or Perl I imagine; thus far I just built
Python) bindings, can I build a transaction on the server-side
in-memory. I essentially want to merge a change into another location
automatically iff it is conflict-free because the original files are
identical (guaranteed conflict-free merge).

In this instance, each release generally contains about 8000 files and
is about 35 Mb. Many commits to trunk (usually of <= 20 files) will
automatically need to commit to 2 or 3 releases.

One idea would be to only checkout some things -- i.e. use
non-recursive checkouts -- which could be a huge savings in most
instances, but from what I've seen reported to the mailing lists here,
non-r checkouts suffer some significant bugs.

Maybe if I build a very selective WC myself with the bindings, the
non-r checkout-related bugs won't rear themselves?

Any ideas about all this?

Btw: this is all part of my effort to simulate the useful
functionality that allows 'linked' files in CMVC across releases. I
think this is similar to what some people have discussed wrt some
shared files in VSS too. In this case, we are going to define our
repository layout so we can make some assumptions and write tools to
those assumptions.

-Travis
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 24 01:17:47 2005