On Thu, Jul 8, 2010 at 7: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. > > Because the svn transport svn:// is the standard, > internal transport for svn, every svn client should > support it.
Yup: if you don't have the HTTPD or Apache include files installed, known as the "httpd-devel" package under RPM based Linux distributions like RedHat and Fedora, you can't build the relevant software because you lack the compilation tools. The "./configure" script detects this and disables the relevant features. > (2) When i attempted to download a single-file, > svn complained that the file name was not a directory > name and rejected the request. You can't "check out" a single file, You can download it with the "export" command, or a simple "wget". > Is this true, that "some svn clients do not support http"? This seems > unlikely to me. And I found > no examples when I searched google. I believe this user is on a Solaris > machine. > > Also, should he be having trouble downloading a single file? I can address > this second issue > with him - I primarily wanted to get the list's input on the first question. > > Thanks very much, > > Jason Aubrey > He's probably trying to check it out, not download it. Checkouts create that ".svn" subdirectory, with its attached information about the other contents of the directory.
