[postgis-tickets] [PostGIS] #3888: Split core and raster extensions

[PostGIS]

#3888: Split core and raster extensions
--------------------------+---------------------------
  Reporter:  strk         |      Owner:  pramsey
      Type:  enhancement  |     Status:  new
  Priority:  medium       |  Milestone:  PostGIS 2.5.0
 Component:  postgis      |    Version:  trunk
Resolution:               |   Keywords:
--------------------------+---------------------------

Comment (by robe):

 >>  postgis_topology is not as intimately tied to postgis as raster is.

 > Can you tell more about this intimate ties ? They are not clear to me.
 > Should we discuss on the list, btw, rather than here ?

 1) postgis raster has GUCS that affect it's behavior -
 http://postgis.net/docs/manual-2.4/reference.html#PostGIS_GUC  it would
 seem a bit odd to register gucs in postgis for a separate extesnion.
 postgis_sfcgal actually has a similar issue but not quite since it's gucs
 are to swap out postgis same named functions with its own.  So utiltizing
 the backend doesn't actually require postgis_sfcgal to be installed.

 2) postgis rasters whole index framework is built on top of postgis
 geometry.  Granted this doesn't affect install and deinstall, but it's
 intimate to me.

 Sure let's propose both options on mailing list, but I'm pretty tired of
 repeating myself and granted it does take a very deep level of
 understanding of how extension glue is setup, I suspect people will just
 say  postgis_raster as a separate extension, that seems okay to me without
 thinking about the deep ramifications this has.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3888#comment:7>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.