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

Re: CVS & Subversion evaluation

From: Early Ehlinger <earlye_at_respower.com>
Date: 2004-02-19 22:02:57 CET

On 19 Feb 2004 kfogel@collab.net wrote:

> Early Ehlinger <earlye@respower.com> writes:
> > SVN has a few weird quirks - there does not appear to be a simple way to
> > make a non-working-copy-directory into a working-copy-directory aside from
> > doing a checkout, for example.
> CVS has this?

Honestly, I don't know. As I said, I'm transitioning from SourceSafe and
my experience with CVS has been, er, minimal.

In SourceSafe, the normal approach is to set a "working directory"
property for a folder in the repository. Actually, it's in the local
config file for the repository - probably somewhere in the windows
registry. But you don't do anything to the working-copy-directory per se.

In any event, I still believe that something like this would be very nice:

$ mkdir svn
$ cd svn
$ svn switch https://foo/repos/ .
and not have it say this:
svn: '.' is not a working copy

A couple of other minor quirks that were brought to my attention by my

$ mkdir tmp
$ cd tmp
$ svn -N co https://foo/repos/ .

Does not create any child folders (according to my teammate, the CVS
equivalent does). What this means is that if you then do something like

$ svn -N co https://foo/repos/ .

and repos only has project folders beneath it, then the following
statement will give you an empty result:

$ ls

What he was expecting was to be able to do the svn -N co..., and then use
ls to figure out which folders to co afterwards - thereby avoiding a co of
the whole repository. Here's the workaround we've pieced together for
that one:

$ svn -N co https://foo/repos/ .
Checked out revision /n/.

$ svn list -r COMMITTED

$ svn -N co https://foo/repos/folder
svn: Working copy 'folder' not locked
  # NOTE: I believe this error message should not occur, but
  # it's easy enough to get around this:

$ cd folder

$ svn -N co https://foo/repos/folder .
  # (or)
$ svn -N update

One big drawback to this workaround is you have to compose the correct URL
all the time. It would be nice to have svn -N -relative co {folder} - and
svn would take the URL from svn info and simply append {folder} to it.

Best Regards,
- Early Ehlinger - CEO - ResPower, Inc - 866-737-7697 - www.ResPower.com 
- 500+ GHz Self-Service Super-Computer from $0.50/GHz*Hr
- (yes, five hundred gigahertz.  point-five terahertz.)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 19 22:05:28 2004

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

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