On 9/26/07, Max Bowsher <maxb1@ukf.net> wrote:
> Erik Huelsmann wrote:
> >> (2) Given that SWIG is not required to build the bindings from a
> >> release, only to do development on them, or to be a release manager, I
> >> see no reason to support versions more than one year old, if even that
> >> much. If we adopted that policy, we would drop support for all versions
> >> prior to 1.3.29 immediately, and in two months time, drop support for
> >> all versions prior to 1.3.31. Or, we could just go ahead and drop
> >> support for all versions prior to 1.3.31 right now.
> >
> > If we drop it in 2 months, given the low number of people impacted,
> > why not drop it right now?
>
> Well, yeah, that's what I was implying in my last sentence above.
Does Subversion build on Windows with VC6 and VS.NET using SWIG
1.3.31? I vaguely recall that some Microsoft compiler choked on the
output of newer versions of SWIG.
Assuming that Subversion builds on all platforms with a given version
of SWIG, I'm +0 on blessing a single version of SWIG as the 'best
version of SWIG' for a given release.
If we also drop support for versions of SWIG other than the officially
blessed one that's fine with me. Is it okay with everyone else,
though?
I do know that there are users who run './autogen.py && make
extraclean-swig' so that they can rebuild the bindings with their
personal version of SWIG, although I'm not sure why they do that.
Cheers,
Daivd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 27 00:17:38 2007