[postgis-devel] The limits of integration

[Mateusz Loskot]

On 15/09/10 20:33, Paragon Corporation wrote:
> Pierre,
> I think having the .so/dd be separate for now is fine and I would keep it
> that way until we confirm the whole project builds together.  
> 
> 
> The SQL file should be kept as a separate file as postgis.sql.in.c is
> already too big.
> 
> I kind of like the way we handled geography.  The geography.sql.in.c  file
> is maintained as a separate but then gets merged in to build the
> postgis.sql. 
> 
> At any rate it should stay as a separate rtpostgis.sql.in.c   file like the
> geography does to keep things a bit sane and then in the final build gets
> tacked on to postgis.sql, but I don't see the need to do that right away.
> 
> I think we should just bring all the raster stuff in as separate.  Do a
> couple of builds with it being part of the make file but built as separate
> dll/so .sqls and then when all looks stable then dissolve the boundaries.

I agree.

I also agree with Pierre's suggestion to change files naming (e.g.rt)
to raster, after the type as it is done with geography.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org