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

Re: Visual Studio.Net and Subversion - another vote

From: Lars Immisch <lars_at_ibp.de>
Date: 2004-03-08 23:46:01 CET

Kevin Williams wrote:
> I'm still a newbie, but does it have to be even that complicated? How
> about:
> // svn_wc.h
> #ifdef WIN32
> #define SVN_WC_ADM_DIR_NAME "svn";
> #else
> #define SVN_WC_ADM_DIR_NAME ".svn";
> #endif
> The folder is flagged as 'hidden' on my system by default, so that should
> meet the "hidden folder" design. If the period starting the folder name
> is the true problem, doesn't this solve it?

Craig Ching replied:

> I think the problem people have with this is that you can't pick up the wc
> and move it somewhere else without having a modified svn program on that
> system. For example, you can't move a Windows wc to Linux.

Arild Fines replied:

> How many people actually *need* that? Isn't half the point of using a vcs in
> the first place to get away from having to "share" source trees between
> different environments/users?
> If I were working on a project in both unix and windows(which I am, to some
> degree), I'd rather have a separate working copy for each environment.

<clever hitchhiker quote snipped>

I agree with Arild.

If the .svn folder is called '.svn' on Unix, and 'svn' on Windows, very
few people will suffer.

Ideally, the 'svn' folder would be hidden (the APR should support hidden
files. At least APR_FILE_ATTR_HIDDEN is defined in apr_file_io.h)

The ones who use vs.net in conjunction with IIS will be happy. All other
Windows users probably won't mind because they see Folder names starting
with a '.' anyway (and only see hidden folders if they explicitly want)

Only the ones who routinely share checked out subversion working copies
with other operating systems will suffer.

I doubt this will be many people; and these people will probably
understand the contents of the .svn directory in the first place and
won't mind to remember that they need to rename '.svn' to 'svn' or vice

I believe the best compromise is:

- to accept the proposed very simple patch

- extend the documentation with a warning that sharing working copies
between machines is not supported (but may work, on your own risk, and
ah, keep in mind that '.svn' is 'svn' on Windows)

I volunteer to produce a proper patch with the hidden flag on Windows
and the documentation.

- Lars

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 8 23:49:01 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.