On 12/03/04 00:34:28, John Lenz wrote:
> And secondly, the only people that would need to upgrade to SWIG are
> developers of subversion. SWIG can even be run from the source directory
> without installing it. That is, you don't even need to install it. If
> you download SWIG, you should be able to do ./configure && make, and then
> in subversion run ./configure --with-swig=~/path/to/SWIG/preinst-swig.
> preinst-swig is a script that runs swig from the source directory. (It
> sets up the right paths for the data files that would normally be located
> in /usr/share/...) Since SWIG no longer has any runtime libraries, a
> SWIG install just consists of the swig binary and the associated data
> files. You don't even need to have perl installed to generate perl
> wrappers.
You could actually incorporate SWIG as part of the subversion build process
similar to the way apr and neon can be compiled from the build directory.
That is, if SWIG 1.3.24 is not installed, the developer could just download
SWIG and extract it into the subversion source directory. Subversion would
then run ./configure and make in the SWIG directory, and then use the
preinst-swig script during the wrapper build process. Since there is no
runtime dependence on anything swig and swig can be run to produce the
wrapper code without being installed, this will work fine. The releases
are tagged in the SWIG CVS, so you could check out the release that way as
well.
If you do this, the only issues would be those of regressions in 1.3.24 vs
1.3.21 since you wouldn't be forcing a new tool on developers.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 3 08:57:22 2004