"Molle Bestefich" <molle.bestefich@gmail.com> wrote on 04/18/2006 10:13:13
AM:
> Mark Phippard wrote:
> > I would argue that we are not introducing any confusing behavior that
> > will be hard to document.
>
> Ok. Perhaps we could dumb it down a bit - not because anyone here is
> dumb, but because testing the thesis would be the easiest way to end
> this particular discussion.
>
> I'd document "checkout" and "integrate" like this:
> ################
> checkout)
> Check out files from a repository into a new working copy.
>
> integrate)
> Convert local files to a working copy, given the URL of a repository
> path that the local files are supposed to match.
> ################
>
> Unless you think I'm being totally ridiculous, I'd appreciate if you
> could show me how to clearly document your variant of checkout?
Doesn't it just come down to how one defines a "new working copy"?
In my particular case, I am interested in this for Subclipse and our
Eclipse integration. When we do a checkout, we have to first let Eclipse
create some local project structure. This can often include some of the
same files that are going to be checked out from the repository. So we
have to look at everything Eclipse created, see if it is in the
repository, and then delete it before starting the checkout. This is not
too big of a problem, but there is also another common scenario that is a
problem. For various reasons, someone disconnects their local project
from SVN or maybe they are just starting with SVN and already have a copy
of their project. They then want to connect it to SVN. Since the CVS
plugin that comes with Eclipse allows all of this, they expect our plugin
to do so as well. We can't provide this feature because we have no way of
turning their local project into a working copy. With this change to
checkout, I could just do a checkout right on top of the local project and
let things work themselves out.
Command line users have expressed the same desire, it particularly comes
up as projects such as KDE migrate from CVS to SVN and all of the
developers around the world want to just convert their local CVS working
copy over to an SVN working copy. Ideally, they would also like it to do
this intelligently and skip the download process as much as possible, but
we are deferring that idea for now.
As John Peacock pointed out, it might make sense to require the use of
--force or some other switch to get this behavior. We can deal with that
once we have the primary functionality actually working.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 18 16:43:45 2006