On Thu, Jul 8, 2010 at 6:05 AM, Jason Aubrey <aubre...@gmail.com> wrote: > Hi All, > > I recently set up svn over http for a project I'm involved with. One > user made the following complaints: > > (1) Some svn clients do not support the http protocol. This > is a common occurrence when a user builds svn from source.
Yes and no. Almost every binary available supports the HTTP protocol. I would even go so far as to say they all do, but somewhere is an obscure client (maybe for some Thuderbird Basic OS system) that doesn't. A much more likely occurrence is that someone builds their own binary and doesn't have the neon and APR libraries needed for building with the HTTP protocol. That binary would not support HTTP. However, you can get pre-build binaries for almost every single OS you can name. There should be no reason why a developer needs to build their own. Your developer can go to http://www.sunfreeware.com to get a Subversion client that uses the HTTP protocol for his Solaris machine. > (2) When i attempted to download a single-file, > svn complained that the file name was not a directory > name and rejected the request. Subversion only allows you to check out directories. You can use the "svn cat" command to get single files, but if you're doing a checkout, you need to checkout a directory. NOTE: You can use the --depth=empty switch to checkout a directory with no files in it, then do an "svn update <fileName>" to get the single file you want. I discourage developers from doing this because what they're doing is making a change without any testing. That is a no-no. -- David Weintraub qazw...@gmail.com
