On 18.05.2011 23:27, Bert Huijben wrote: > >> -----Original Message----- >> From: Hyrum K Wright [mailto:[email protected]] >> Sent: woensdag 18 mei 2011 23:22 >> To: [email protected] >> Cc: [email protected] >> Subject: Re: svn commit: r1104160 - >> /subversion/trunk/subversion/libsvn_subr/utf.c >> >> 2011/5/18 Branko Čibej <[email protected]>: >>> On 17.05.2011 14:16, Hyrum K Wright wrote: >>>> apr_atomic_xchgptr() and friends are not available on APR 0.9. (This >>>> is causing a buildbot build failure.) >>> Maybe we should just drop support for APR-0.9 finally? I know that we >>> sort of "promise" to support it, but really, it's been obsolete for years. >> Yah know, I've been wondering the same thing for a while too. While >> there might be a theoretical problem in changing our guarantee, I >> don't think there will be a practical one. (Certainly far less that >> what may happen with other 1.7 changes.) > What does the apr project say about 0.9 support? > > If they stop supporting it, we can too I suppose.
APR-0.9 is "supported" simply because there's still a not-insignificant number of httpd-2.0 servers out there. There was a security release of 0.9 fairly recently. We're sort of on the same boat because svn-1.0 supported apr-0.9 (since there was no apr-1.0 at the time), even though we strongly recommend against using that version because of various problems it has, the most notable being broken support for large files. We're really exposed because we use APR types in our public APIs, but on the other hand, anyone who upgrades their APR from 0.9 to something newer will most likely have to rebuild Subversion anyway, because of ABI incompatibilities. -- Brane
