[postgis-devel] The limits of integration

[Paragon Corporation]

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.

Just my 2 cents,
Regina

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Pierre
Racine
Sent: Wednesday, September 15, 2010 2:17 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] The limits of integration

Hi,

So I guess there are some limits to the integration of the raster part. I
guess we want to keep a different shared library and a different .sql file?

The shared lib is now named rtpostgis. Ok with that name? Or should it
becomes postgisrt-2.0.so? Or something else?

The official name of the raster extension should now be "The PostGIS RASTER
type" in place for the "bad" "WKT Raster".

Thanks,

Pierre

_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel