Sander Striker <striker@apache.org> writes:
> It seems like overkill to me. The only thing that is troublesome is
> libtool. In the buildcheck --release code we can do the check for
> the correct libtool version and then ask a question:
>
> """
> libtool 1.4.3 detected in <path>. If this is the libtool that comes
> with your system it is possible that it has vendor patches applied,
> which is known to cause problems. You can find a pristine version
> of libtool 1.4.3 here:
>
> <url_to_libtool>
>
> Are you sure that a pristine libtool is being used? [y/n] .
> """
>
> A simple solution that simply reminds the RM what is up. No need
> for anything more difficult IMO.
That's probably enough. Indeed, I had assumed the tools were
*already* doing this for me -- since the libtool check failed on one
platform during buildcheck, I assumed that when it didn't fail
somewhere else, everything must be all right. Of course, everything
was all right for just a build, but not for a dist. Which means
dist.sh should do a stricter check than buildcheck does.
Since I have this problem on my home machine, I'll take a look at
making such a check.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 24 16:51:08 2004