[postgis-tickets] [PostGIS] #3338: postgis extension that returns not supported for all Raster functions if raster not available

[PostGIS]

#3338: postgis extension that returns not supported for all Raster functions if
raster not available
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.3.0
 Component:  postgis  |    Version:  2.0.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by gdt):

 It would be completely unreasoable to include gdal sources.   This results
 in duplicated code and also means that postgis needs a security release
 immediately when there is an issue in gdal.

 I think the real problem here is that gdal should be set up to build core
 and modules so that it can be separate packages, and postgis can depend
 only one the core part.

 Also, how big does gdal end up being, compared to postgresql itself?  The
 gdal-lib pkgsrc package on NetBSD 6 i386 is 94M including things it
 depends on.  postgresql seems more like 25 MB.   Still, that leaves
 postgis and everything it depends on at 164 MB.

 Is the FreeBSD gdal package much bigger?  (pkgsrc's does not yet have
 python bindings, which clearly should be split.)

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