[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: API proposal - issue 2188 - svn_client_copy/move

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-10-28 01:38:45 CEST

On 10/27/05, Madan U Sreenivasan <madan@collab.net> wrote:

> I see that after a patch and rejecting it too, nobody seems to exactly
> know what is to be done regarding this. So, here am proposing what I
> think is right. Pl. feel free to criticize(and hey, dont forget to
> suggest an alternate ;) )
> The pain area as of now is
> - The inability to return error when the destination folder already
> exists
> The compatibility issue as of now is
> - svn client behavior should be retained
> I propose a simple extra parameter - on_dir_exists to the copy and
> move API that dictates how to handle the situation of the directory
> existing
> a value of
> svn_error_if_dir_exists - does exactly that
> svn_make_sub_dir_if_dir_exists - does exactly that
> with a default value of svn_error_if_dir_exists.
> Other problems
> Ability to copy multiple source urls to a single destination url, when
> implemented would need to call the copy/move API, with a on_dir_exists
> value of svn_error_if_dir_exists and can be built around this solution.
> I'd like comments on the idea(including the variable names/values
> etc.,)

If we're going to add a parameter to control this kind of behavior,
I'd also like to add the ability to overwrite the file/directory
that's present in the destination. To be really useful this should
also apply to copy in addition to move. This is a fairly commonly
requested feature (say for example if you want to have a "currently
installed version" tag, whenever you recreate it you have to do a
delete then a copy).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 28 02:00:53 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.