On Thu, Jul 8, 2010 at 10:13 AM, Campbell Allan
> On Thursday 08 Jul 2010, Nico Kadel-Garcia wrote:
>> On Thu, Jul 8, 2010 at 7:05 AM, Jason Aubrey <aubreyja_at_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.
> Are you certain about that? Neon or serf provide the client with http support
> and are both in the subversion-deps source tarball. I'm fairly sure all the
> machines I've compiled on have never had the httpd-devel like packages
> installed (or in some cases any dev packages beyond the compiler). https
> support can be tricky as this will require either the openssl dev package to
> be installed or a local build handy.
You seem to be correct. It's the neon *include* files, not merely the
libraries, that are needed to compile some of this behavior in
standard Fedora and RHEL setups. I've not tried it with serf.
As pointed out elsewhere, it's mod_dav_svn that needs httpd related
utilities. Mind you, picking and choosing bits to leave out of a
Subversion setup is like picking the wrench you won't need in your
toolbox. If you're squeezed for space, leave one out, but it's
inevitably the one you didn't bring that you turn out to need....
Received on 2010-07-09 01:43:02 CEST