On 9/28/07, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> On 9/27/07, Max Bowsher <maxb1@ukf.net> wrote:
>
> > Users of enterprise, slow-update-cycle, distros should be using
> > Subversion release tarballs, not svn checkouts, and thereby be unaffected.
>
> To be utterly clear: from the user's point of view, there is no
> compile-time or run-time dependency on any particular version of swig.
> The svn release tarball ships with bindings that are
> ready-to-compile, with no external dependencies.
>
> So it's irrelevant what version of swig happens to ship in any
> particular linux distro. The *only* people who need a certain version
> of swig available are svn developers building from a working copy.
It was always clear that SWIG was optional for users and developers
who don't touch the bindings.
It's just that many developers use the same slow release distros as
the users (its called a "day job" :-). So touching the swig bindings
(with a 1.3.31 requirement) means building and installing swig from
scratch.
Which is fine if you get something for it. So far, no one has said
what is the gain is of requiring 1.3.31 instead of 1.3.27. There were
comments that 1.3.25 was a bit change, but nothing more specific than
that.
Ubuntu 6.06 LTS (dapper) has 1.3.27
Ubuntu 6.10 (edgy) has 1.3.28
Ubuntu 7.04 (fiesty) has 1.3.31
I'm just trying to keep the developer barrier to entry as low as is
practical ('cause it might make my life easier :-).
-Dan C
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 28 17:49:13 2007