Dirk Hoffmann wrote:
...
> One java program copies files into the repository another one retrieves
> the files from the repository (simplified version). I'm using the
> javahl-binding as a bridge from java to subversion.
...
> What I don't need are working copies as no user has direct access to the
> repository and no editing takes place on local copies.
...
> But things are getting complicated when a new version of an already
> existing file needs to be put into the directory which is the most
> frequent use case.
>
> At the moment this is my receipt to achieve that:
>
> 1. Checkout the file's parent directory into a temporary working copy.
> 2. Copy the new version of the file into the working copy overwriting
> the previous version
> 3. Commit change providing a log message
> 4. For administrative reasons get the number of the head revision.
>
> Doing so has the disadvantage of checking out not only single files but
> entire directories. There is also a big overhead for creating the
> working copy's directory structure.
...
> If there was a way to copy new versions of files into the repository
> without needing a working copy subversions range of use cases would be
> much broader.
There is. But not with the java bindings or svn command line client.
You would need to either enhance the java bindings, or write an external
program (in C, python or perl) and run that.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 26 19:50:41 2004