[Gdal-dev] CVS

[Howard Butler]

Some reasons for keeping them in CVS:

1)  GDAL has history of keeping generated code in the CVS tree.  The 
old-style Python wrappers, which are generated from swig 1.1, pretty 
much *have* to be pushed into the tree because Frank is the only 
person I know of with swig 1.1 installed anywhere.

2) SWIG is in severe flux right now.  1.3.28 was a *major* release, 
complete with incompatibilities, bugs, and API changes.  The distros 
all vary in the swig that they provide, and this can have a great 
impact on what people see when they generate bindings themselves. 
1.3.29 came quickly (and still has some broken Python things).

3) Windows

Some reasons for dropping them from CVS:

On the flip side, I agree that having the generated bindings in CVS 
is a pain.  They almost always seem to generate CVS conflicts and 
sync'ing between the various flavors is not always consistent.  I 
almost always generate my own bindings with the swig I have installed 
when doing any development.  I agree that a 'make dist' target should 
be generating *all* of the bindings for each language flavor anyway, 
regardless of whether or not we keep the bindings actually stored in 
CVS.

Howard


At 4:38 PM +0300 4/6/06, Ari Jolma wrote:
>So I'm a committer.
>
>My first suggestion concerns the swig generated wrapper codes and
>modules. Let's remove them from CVS, shall we? GEOS has this policy and
>it just makes sense. Generation of them should be left as a subtask to
>"make dist".
>
>Regards,
>
>Ari
>
>--
>Prof. Ari Jolma
>Kartografia ja Geoinformatiikka / Cartography and Geoinformatics
>Teknillinen Korkeakoulu / Helsinki University of Technology
>tel: +358 9 451 3886 address: POBox 1200, 02015 TKK, Finland
>Email: ari.jolma at tkk.fi URL: http://www.tkk.fi/~jolma
>_______________________________________________
>Gdal-dev mailing list
>Gdal-dev at lists.maptools.org
>http://lists.maptools.org/mailman/listinfo/gdal-dev