On 23.08.2015 23:27, Stefan Fuhrmann wrote: > The latest relevant section taken from that issue: > > Secondly, I would like to install Subversion 1.9 to try it out, but I'm > running >> CentOS 6.4 and I just can't get Subversion 1.9 to build. As I mentioned >> below, I >> have to download the latest Serf version, which doesn't come with CentOS 6.4. >> And building serf doesn't work. I try just "scons", but then "scons check" >> fails >> with things like "test/test_buckets.c:1559: warning: integer overflow in >> expression". Plus scons wants "APR", "APU", "OPENSSL", and "PREFIX" >> parameters >> (according to the README.TXT). I'm sure my APR path isn't correct---on this >> server I used the Apache from yum and don't know where my APR libraries are. >> I >> don't even know what APU is. So it seems highly unlikely for me to get >> HTTP(S) >> support on Subversion 1.9. The Subversion build process is and has always >> been >> an utterly brittle mess. See Bug 4589 >> <http://subversion.tigris.org/issues/show_bug.cgi?id=4589>, which indicates >> my frustration. >> >> > Is there anything we can reasonably do about it?
Other than reduce the number of dependencies? Not really. Building from source is always non-trivial, especially building from scratch. The fact that Serf uses scons is hardly an additional complication; their README file explicitly mentions apu-1-config, one only has to actually read the file instead of stopping at the first thing that looks like a build command line. Other than getting the dependencies lined up, a simple 'configure' with no additional parameters will usually work for Subversion. It becomes more interesting when you have a heavily customized system, but there's not much we can do about that other than providing the knobs to tweak the build. Given that this exists: http://opensource.wandisco.com/centos/6/svn-1.9/RPMS/x86_64/subversion-1.9.0-1.src.rpm I have to wonder what these guys are doing right that Garrett isn't. -- Brane
