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

Re: [ericsmith@windsor.com: RE: Cygwin Install, Misc. Documentation and Install Comments]

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-01-09 23:03:43 CET

Andrew <asha@onezero.org> writes:

> (1) In order to get svn to work I've had to use absolute Windows
> paths for the repository URL, e.g.,
> svn co file:///c:/cygwin/home/Andrew/my_repository
> I tried many variations on this and this is the only one that I
> could get to work.
> Right now I use a shell variable called "r" that's set to the path
> to the repository, and right now I'm only using one repository, so
> things aren't too bad, but still, the situation is less than
> desirable. I'd like to be able to do things like
> svn co file://~Andrew/my_repository
> or at least
> svn co file:///Home/Andrew/my_repository
> (The path Home/Andrew maps to C:/cygwin/home/Andrew.)

So this problem is really just part of your request for svn to
understand cygwin paths. As expected, "true" win32 paths still work.

> (2) When I do a commit, and svn tries to invoke the editor so that I
> can write a commit message, svn doesn't understand my EDITOR variable,
> because it's expressed in terms of the Cygwin file system and not the
> Windows file system:
> $ svn commit FunctionMain.cs
> The system cannot find the path specified.
> svn: Error calling external program
> svn: Commit failed (details follow):
> svn: system('/usr/bin/vim svn-commit.64376.00001.tmp') returned 1
> $ echo $VISUAL
> /usr/bin/vim
> | echo $EDITOR
> /usr/bin/vim
> $

And this looks like a request for svn to understand cygwin environment
variables, rather than "true" win32 variables.

(By "true", I mean the things actually supported by the win32 API, and
not the cygwin layer on top of it.)

> I expect to find more things like this. So far, after considerable
> time, I've been able to find workarounds for every barrier that I've
> encountered, but as a new Subversion user my experience on Cygwin has
> not been very fun.

Your problems aren't unique. You're experiencing what anyone would
experience when running a native win32 commandline program within

The solution here is to stop running the win32 binary under cygwin.
Run a cygwin-compiled binary instead.

> As I recall, this is the Subversion binary that was distributed
> tigris.org. I'm using the binary instead of a Cygwin-built version
> because I couldn't find an existing Cygwin-built binary on the web, and
> my attempts to build Subversion on Cygwin failed.

Why did it fail? As I mentioned in an earlier post, I've compiled
under cygwin many times, and had no problem. Brandon Ehle compiles
and uses the svn client under cygwin, using today's code.

> My suggestion is that the project distribute a for-Cygwin binary
> that understands the Cygwin file system.

If any of our developers were active cygwin users, I guess we could do
that. Wanna volunteer? :-)

The real issue here is why you weren't able to build svn under
cygwin. If you could do that, your pain would be over. Wanna tell us
what happened?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 23:06:33 2003

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.