[postgis-devel] Vote on Merging postgis and raster installs and when

[Sandro Santilli]

On Mon, Jan 02, 2012 at 01:36:13AM -0500, Paragon Corporation wrote:
> Do we want to do this.  We said we did at the code sptring.  Are we ready?
>  
> The main reason we had kept the installs separate is because building with
> raster was much harder because of the python dependency.  Now that python is
> no longer required and compiling GDAL is not that big of a deal (and in fact
> something the postgis geometry/geography might find useful alter on) , can
> we merge?
>  
> +1 from me
>  
> Granted I don't know how much effort is involved.  Right now the
> extensions/postgis folder does have them merged
>  
> So when you do  CREATE EXTENSION postgis; or  ALTER EXTENSION postgis UPDATE
> TO "2.0.0a13";
>  
> You get both postgis geometry/geography and raster support and update both
> postgis geometry/geography/raster
>  
> So it's just the old way of installing postgis that is still separated.
>  
> This of course also requires that Chris works out the builbot issues with
> why topology and raster aren't being tested.

I'm not a big fan of monolithic systems.
What's the rationale for forcing anyone who only needs vectors to also have
support for rasters ? 

Seems more of a packaging issue to me, and I see packagers usually do more
splitting than upstream (breaking packages in -core, -dev, -utils, -doc, ...)

--strk;

  ,------o-. 
  |   __/  |    Thank you for PostGIS-2.0 Topology !
  |  / 2.0 |    http://www.pledgebank.com/postgistopology
  `-o------'