On Jun 11, 2007, at 17:28, Erik Huelsmann wrote:
> On 6/11/07, Kendall Shaw wrote:
>
>> Erik Huelsmann wrote:
>>
>> > On 6/11/07, andreas kollenbach wrote:
>> >
>> >> i tried to compile subversion 1.4.3 with a newer neon library than
>> >> version 0.25. But the config script insists on version 0.25.5.
>> >>
>> >> What's the reason for that behavior?
>> >> Is there any incompatibility between a lib > 0.25.5 and
>> subversion?
>> >
>> > Yes: from the Neon site: "The neon API is subject to
>> > backwards-incompatible change over minor versions (0.24.x ->
>> 0.25.x)
>> > but is stable across patch releases (0.24.0 -> 0.24.x)."
>> >
>> > This means that new minor releases need to be explicitly
>> verified to
>> > be backward compatible, or the sources need to be adjusted for
>> the new
>> > version...
>>
>> I notice that the INSTALL file says you need 0.25.5 or 0.26.1. So,
>> shouldn't that mean that the latest neon is compatible?
>
> Yes, it does mean that. We have had problems in the past with new neon
> versions so that we turned to a strategy where every release was
> blessed separately. We currently haven't backported the 0.26.3
> blessing to the 1.4 branch. I don't expect problems however.
FYI: Perhaps inadvisably, MacPorts has been building Subversion
without Neon version checks since 2006-01-25.
http://trac.macosforge.org/projects/macports/ticket/6783
It looks like this was done back in the days when Subversion didn't
support Neon 0.25.5. MacPorts currently has the deficiency that you
can only ever install the current version of a software package,
never an earlier version. So as soon as somebody would update the
Neon port, Subversion couldn't be compiled anymore...
In my limited use I haven't noticed any problems from using
Subversion 1.4.x with Neon 0.26.x.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 12 01:28:24 2007