On Mon, 2005-01-10 at 18:37, Justin Erenkrantz wrote:
> Now that 1.3.24 is out, we should investigate whether we want to bump
> everyone up to that: but, as we understand it, it's not practical to
> support 1.3.19-1.3.21 and 1.3.24 at the same time. So, that really places
> me in the camp that we should hold off a bit on 1.3.24 to see if the SWIG
> folks change their mind yet again on how things should work... *sigh* --
> justin
I think you're making two errors here:
(1) Although it's not explicit, I think you're making a moral judgement
against swig here, without understanding that their 1.3.x line is like
our 0.x line--no compatibility guarantees whatsoever. It was our
decision to build our release on quicksand.
(2) Practically speaking, our situation with swig 1.3.24 will be much
better than it is with 1.3.21 because there is no runtime library to
depend on. Even if swig 1.3.25 changes everything, we won't have to
require that people have swig 1.3.24 *installed*, only that they have to
drop it into the build tree in order to build. And we can ship it as
part of our tarfile, of course.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 11 18:49:37 2005