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

Re: [PATCH] new feature: takeover

From: Dan Sandberg <x_at_cs.stanford.edu>
Date: 2005-08-05 05:04:32 CEST

I've definitely needed this kind of functionality a number of times.

I'm a developer, but not a Subversion developer, so please excuse my
ignorance. :)

Isn't there some way to leverage the existing rsync tool rather than
re-writing it or integrating it into Subversion?

It seems like ultimately we want a command like:

svn co svn://repository/app local_app --use-existing

Which does steps:

[1] cp -a local_app tmp_versioned_local_app
[2] rsync -a svn://repository/app tmp_versioned_local_app
[3] rsync -a local_app tmp_versioned_local_app
[4] rm -rf local_app
[5] mv tmp_versioned_local_app local_app

Step [2] being the problem. Step 2 would efficiently copy the head
revision ( as it would appear if a client did svn co
svn://repository/app, including .svn directories ) to the local
computer. This seems doable with svnserve but I don't know how/if it
could be done with mod_dav_svn. Is there a project policy against
relying on external dependencies like rsync? Since it would not be core
functionality could svn just output 'rsync not available' if it could
not be found? Is there a non-GPLed version of rsync that could be used
without introducing GPL dependencies?

It just seems wrong to add a poor version of rsync to Subversion...



Ben Collins-Sussman wrote:

> On Aug 1, 2005, at 5:07 PM, Greg Hudson wrote:
>> On Mon, 2005-08-01 at 22:49 +0100, Julian Foad wrote:
>>>> 1. this is a good idea, a useful new feature. very much in demand.
>>> +1.
>> Where are people getting this impression from? I don't watch the users
>> list, but from my perspective this is a weird use case which came up on
>> the dev list after several years, and is something you'd want once and
>> could work around most of the time.
> I think our years of using CVS have blinded us to how lame 'import'
> really is.
> Nearly every user I've seen who is utterly new to version control is
> surprised/confused/disappointed when he realizes that 'svn import'
> didn't convert his tree into a working copy. "I have to redownload
> the whole thing again???" Heck, I even remember running into this
> when I first tried CVS.
> Sure, we have a clever workaround -- create an empty repository dir,
> check it out into the unversioned tree, svn add, svn commit -- but
> this isn't obvious to newbies.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 5 06:05:07 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.