If there's no integration *required* to make the Ruby stuff work well, then (a) you should keep them and (b) we should strip out the old ones and replace them with a readme.txt pointing to the location of the maintained ones.
P. On Wed, Dec 1, 2010 at 8:31 AM, strk <s...@keybit.net> wrote: > On Wed, Dec 01, 2010 at 11:26:16AM -0500, J Smith wrote: > >> The big question is: do we want to have this code directly in the main >> GEOS repository? We were planning on using github to facilitate the >> whole social coding scene thing and 'cause we like the dead-simple >> release management that jeweler provides. > > I second using a separate repository. > That way you can keep binding release cycles completely separated > from the core GEOS library. > > I've been too lazy to do that for the PHP bindings... > > --strk; > > () Free GIS & Flash consultant/developer > /\ http://strk.keybit.net/services.html > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/geos-devel > _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel