Ben Reser wrote:
>On Thu, Feb 26, 2004 at 10:16:42PM +0100, Branko ??ibej wrote:
>
>
>>>Someone needs to rebuild with the patches from trunk to fix this.
>>>Relevent revision numbers are:
>>>r8829 and r8834
>>>
>>>
>>>
>>>
>>No, someone else needs to wait until those patches are released with
>>1.0.1 and I build _those_ binaries, or else that same someone can build
>>the current trunk and use that, if they wish.
>>
>>
>
>That's ridiculous. If you're going to release binary packages of the
>bindings then they ought to work. So either you need to rebuild
>*WITHOUT* the bindings.
>
The bindings are in a separate zip file; nobody's forced to use them.
>Or patch them. Considering that this is an
>issue related specifically to Windows, I don't see why you wouldn't
>patch it.
>
>
I am not going to build (public) binaries based on anything but released
tarballs, period. You are free to build your own patched binaries; and
for all I care upload them to the tigris.org server I'm not stopping you
or anyone from doing that (as long as "svn --version" clearly indicates
it's a patched version).
If the bindings in 1.0.0 don't work, that's sad of course, but it's not
the end of the world. Presumably the problem will be fixed in time for
1.0.1, just like any other bug. I don't consider this to be a big enough
problem to yank 1.0.0, or to rush into 1.0.1.
Besides, from looking at the suggested patches, this doesn't look like a
Windows-specific problem to me at all -- nor is the fix correct.for all
platforms. Taking a quick glance at apr's configure.in, I see that
APR_INT64_T_FMT can be any one of d, ld, lld, or qd on Unix-like
systems. FreeBSD+Linux != Unix, everything else != Windows.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 27 00:39:19 2004