Garrett Rooney <rooneg@electricjellyfish.net> writes:
> On 10/27/05, Madan U Sreenivasan <madan@collab.net> wrote:
>
>> 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.,)
Once the library provides an interface with predictable behaviour the
application can implement all the "smart" behaviour on top. Quite how
much of the "smart" behaviour should be moved into the library is a
hard question to answer, one reason for putting it in the library is
that it might be possible to do things more efficiently (fewer RA
calls) in the library than in the application.
> 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).
Are these requests for an application interface, "svn cp/mv", or a
library interface, "svn_client_copy/move"?
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 29 00:24:18 2005