At 07:58 PM 4/13/02 -0700, Sean Russell wrote:
>Is this referred to anywhere else besides in the list archives, or are the
>powers that be unwilling to depend on this software?
I expect eventually it will get committed, though someone can correct me if
I'm wrong and I'll find some other home for it. The "powers that be" are
mostly C guys, so they aren't going to be that familiar with Ant. Also, I
failed to mark the message with a [PATCH] subject line (since these are
actually new files), so it may have slipped through their scripts for
catching such things.
As to whether it should be depended on, well, it shouldn't be. It is not a
part of the standard Subversion build system, just a convenience wrapper
around it to automate as much as possible the rules of the INSTALL file. If
you want to have java and ant on your system then you can use it if you
choose, but those are not requirements for someone using Subversion.
>Anyway, for my part, the initial bootstrap isn't a problem; it's upgrading
>that I always have trouble with, one way or another. I'm not sure that there
>is an easy way to make upgrades seamless, except some sort of chrootted build
>mechanism.
There is a target for update builds called "upbuild", and as I said you can
get rid of shared libraries if you want to take the chance of breaking your
client. However, doing a complete build of absolutely everything from
scratch, including HTTPD 2.0, took just over an hour on my ancient Pentium
Pro machine. If you perform the complete builds from scratch only when you
have problems with an update build, that shouldn't prove too onerous. Or
you could run a cron job to do a complete build every night and send the
results to svn-breakage. Then you would always be up to date.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 14 22:56:15 2002