Gregor, I use the "Apache 2.2" binaries on Windows. It does include svnserve, but so what? The whole installation is about 15 MB. More of that spaced is "wasted" on translations into languages I'll never know than on a binary I'll never use.
Cygwin is a good option, too, if it behaves better for you than it does for me. - Isaac On Tue, Jan 13, 2009 at 9:03 AM, gregor <[email protected]> wrote: > > Yes, that's what I eventually did. I chose the CollabNet svn command > line client option for which I had to sign up for an account. I didn't > originally want to do that, but it became apparent that CollabNet has > close connections to the Subversion project itself, so I became less > averse. I think you might be able to use the zip download options > marked Apache 2.0 and Apache 2.2, but that I believe involves > installing the subversion server as well as the command line client. > > Installing the CollabNet client worked a treat, and it still works > this morning. > > > On Jan 13, 3:25 am, "Ian Petersen" <[email protected]> wrote: >> On Tue, Jan 13, 2009 at 4:10 PM, gregor <[email protected]> wrote: >> >> > Well, finding a "windows command line svn client" looks easier said >> > than done. I've spent over an hour now trying to find a free one (I've >> > got no use for it at the moment apart from this issue), and it's not >> > at all clear that there is one that will do the job without messing >> > about with 30 day trials for Syncro and the like. >> >> Is there a reason you can't use one of the binaries listed >> here?http://subversion.tigris.org/getting.html#windows >> >> I'm pretty sure I've usedhttp://www.sliksvn.com/en/downloadbefore. >> >> Ian > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
