On 8-Jul-05, at 1:20 PM, Branko Čibej wrote:
> Mark Phippard wrote:
>> Try to cut some slack. The Win32 binaries have been coming out on
>> almost the same day as the official release of the source for a
>> while now.
> So they have. And all I have to say to anyone who can't wait for a
> few days ubtil I find the time (usually between 2 and 4 a.m.) to
> build the distro is, with great restraint, "build it yourself."
> After all, what's a few days compared to the serveal weeks between
> patch releases?
Please don't assume that I have a complaint against the time you take
to produce Win32 binaries. That is not my point, and I am thankful
that you do it at all.
I was simply expressing the possibility that the subversion team
could officially include Win32 binaries, and perhaps Mac OS X
binaries as part of the official release.. I only suggest it because
I *assume* that building on Win32 and OS X is a requirement for them
to sign-off on the source tarball, so logically the binaries have
already been built.
The current issue with ZLib, of which I don't know any of the
details, could have been announced on the list as well, just to give
the community an idea of what was going on.
I would build it myself, but I attempted that with 1.1.0 and found
that setting up a Windows machine to build subversion was extremely
painful.. amounting to a wild goose chase of tracking down and
building various other packages of which I knew nothing (Neon, APR,
BDB, install Perl, Python, etc.). I don't need BDB support, so I
suppose it isn't really that bad. I will tackle it again when I find
the time. But it is certainly not standard practice for Windows and
Mac users to have to compile software from source in order to use
it. I know it is more common in the unix environment, but unix users
are very different in terms of their expectations.
I do happen to build subversion on my Mac, because it was simpler
than setting up the build on Windows. (still without BDB support)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jul 8 19:56:03 2005