[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):

 > Yes, if you need both. It's the same you have to do with
 > postgis_topology and address_standardizer etc. Consistent.

 It's not consistent as I mentioned.  First of all address_standardizer
 doesn't even need postgis at all.

 postgis_topology is in it's own schema so can never be part of the postgis
 extension.
 Besides postgis_topology is not as intimately tied to postgis as raster
 is.  It has no support for indexes and doesn't have GUC hooks.

 >>  If people really don't want raster, they should compile
 >>  --without-raster

 > Not everyone can compile its own PostGIS.

 Exactly and my proposal takes care of those people as well.  The only
 inconvenience for them is
 having to know about the new "2.5.0noraster"  while other users don't need
 to know anymore than
 what they do now.

 {{{
 CREATE EXTENSION postgis;
 }}}


 > As for your other proposal (encoding in version) please
 > file a separate ticket so we can discuss it in depth.

 Done at #3890

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3888#comment:4>
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.