John Peacock wrote:
>Max Bowsher wrote:
>
>
>>Not at all... if 0.25.0 is known buggy, perhaps we should make configure
>>reject it too?
>>
>>
>
>Probably not a bad idea. INSTALL should probably suggest 0.25.3 (if that tests
>out OK), but configure should still block on 0.25.0 to be safe.
>
>
Perhaps blocking Neon 0.25.0 outright is a little drastic. Is it
possible to simply add a LARGE warning in the configure script if 0.25.0
is found, mentionning the bug and recommending an upgrade?
We have a known workaround for 0.25.0 (disable http compression), so I
think locking it out completely would be going a little too far,
especially for people building on a system where 0.25.0 is the installed
system library and they don't feel like building their own.
Also, should this go into the release notes? Something along the lines
of "There is a bug in Neon 0.25.0 which can make Subversion fail to
operate with WebDAV repositories. We strongly recommend you use a later
version like 0.25.3, or revert to 0.24.7".
Thoughts?
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 14 15:06:21 2005