require 'formula' class Postgis < Formula homepage 'http://postgis.net' url 'http://download.osgeo.org/postgis/source/postgis-2.1.1.tar.gz' sha1 'eaff009fb22b8824f89e5aa581e8b900c5d8f65b' head 'http://svn.osgeo.org/postgis/trunk/' option 'with-gui', 'Build shp2pgsql-gui in addition to command line tools' depends_on :autoconf depends_on :automake depends_on :libtool depends_on 'gpp' => :build depends_on 'postgresql' depends_on 'proj' depends_on 'geos' depends_on 'gtk+' if build.include? 'with-gui' # For GeoJSON and raster handling depends_on 'json-c' depends_on 'gdal' def install # Follow the PostgreSQL linked keg back to the active Postgres installation # as it is common for people to avoid upgrading Postgres. postgres_realpath = Formula.factory('postgresql').opt_prefix.realpath ENV.deparallelize args = [ "--disable-dependency-tracking", # Can't use --prefix, PostGIS disrespects it and flat-out refuses to # accept it with 2.0. "--with-projdir=#{HOMEBREW_PREFIX}", "--with-jsondir=#{Formula.factory('json-c').opt_prefix}", # This is against Homebrew guidelines, but we have to do it as the # PostGIS plugin libraries can only be properly inserted into Homebrew's # Postgresql keg. "--with-pgconfig=#{postgres_realpath}/bin/pg_config", # Unfortunately, NLS support causes all kinds of headaches because # PostGIS gets all of it's compiler flags from the PGXS makefiles. This # makes it nigh impossible to tell the buildsystem where our keg-only # gettext installations are. "--disable-nls" ] args << '--with-gui' if build.include? 'with-gui' system './autogen.sh' system './configure', *args system 'make' # PostGIS includes the PGXS makefiles and so will install __everything__ # into the Postgres keg instead of the PostGIS keg. Unfortunately, some # things have to be inside the Postgres keg in order to be function. So, we # install everything to a staging directory and manually move the pieces # into the appropriate prefixes. mkdir 'stage' system 'make', 'install', "DESTDIR=#{buildpath}/stage" # Install PostGIS plugin libraries into the Postgres keg so that they can # be loaded and so PostGIS databases will continue to function even if # PostGIS is removed. (postgres_realpath/'lib').install Dir['stage/**/*.so'] # Install extension scripts to the Postgres keg. # `CREATE EXTENSION postgis;` won't work if these are located elsewhere. (postgres_realpath/'share/postgresql/extension').install Dir['stage/**/extension/*'] bin.install Dir['stage/**/bin/*'] lib.install Dir['stage/**/lib/*'] include.install Dir['stage/**/include/*'] # Stand-alone SQL files will be installed the share folder (share/'postgis').install Dir['stage/**/contrib/postgis-2.1/*'] # Extension scripts bin.install %w[ utils/create_undef.pl utils/postgis_proc_upgrade.pl utils/postgis_restore.pl utils/profile_intersects.pl utils/test_estimation.pl utils/test_geography_estimation.pl utils/test_geography_joinestimation.pl utils/test_joinestimation.pl ] man1.install Dir['doc/**/*.1'] end def caveats; pg = Formula.factory('postgresql').opt_prefix <<-EOS.undent To create a spatially-enabled database, see the documentation: http://postgis.net/docs/manual-2.1/postgis_installation.html#create_new_db_extensions If you are currently using PostGIS 2.0+, you can go the soft upgrade path: ALTER EXTENSION postgis UPDATE TO "2.1.0"; Users of 1.5 and below will need to go the hard-upgrade path, see here: http://postgis.net/docs/manual-2.1/postgis_installation.html#upgrading PostGIS SQL scripts installed to: #{HOMEBREW_PREFIX}/share/postgis PostGIS plugin libraries installed to: #{pg}/lib PostGIS extension modules installed to: #{pg}/share/postgresql/extension EOS end end