[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SWIG versions - why not 1.3.31 yet?

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2007-09-27 02:55:21 CEST

Dan Christian wrote:
> The Ubuntu long term support release (dapper) still ships with swig
> 1.3.27. It would be a (needless) pain if that was no longer
> supported. Not everyone updates there OS every 6 months or enjoys
> building swig from scratch.
>
> Given that only developers are affected, what does it mean to "drop
> support"? How much support effort will this really save?

A local swig installation *not* required to build the bindings from a
release tarball. It's only needed to build them from a checkout, or to
regenerate files which are shipped in the tarball.

*** Therefore only people developing Subversion, or deliberately
choosing to rebuild the generated SWIG files despite pregenerated ones
being shipped in the tarball, are affected. ***

Dropping support for older versions of swig saves a *lot* of effort,
since SWIG tends to undergo significant changes - restricting the
allowed versions cuts down the number of different interpretations of
the mappings that developers have to think about.

Max.

Received on Thu Sep 27 02:56:09 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.