John Lenz wrote:
> <rant>If subversion is using a depreciated feature, then you should
> notify the SWIG developers. If the new feature which is supposed to
> replace the depreciated feature does not work for some reason, then
> the new feature needs to be fixed or the old un-depreciated. It's
> frustrating when users ask on the swig mailing lists why subversion
> doesn't work.</rant>
Slow down. It is not up to us to notify SWIG developers of anything.
What we _should_ do is fix our configury to not accept SWIG newer than
1.3.21, until we do support later versions.
> 2) The patch I attach here requires swig 1.3.24, which is not yet
> released. (Although, we are planning on a release sometime this
> week). On the other hand, the runtime dependency on swig is
> completely gone. NO libswigpy is used anymore. After this patch,
> users of the python bindings do not need swig installed.
If this patch requires 1.3.24, then sadly we can't use it as it stands
because there are lots of systems come with older versions.
In general, though, I do agree we should support newer versions of SWIG
(though not at the expense of 1.3.19-21). However up to now, we've not
noticed it being a serious or often-reported problem. Perhaps you should
refer the people that complain to the users@subversion.tigris.org
mailing list.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 30 09:43:19 2004