Next | Query returned 14 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2009-12-17 01:25:36 by Greg Troxel | Files touched by this commit (3)
Log message:
Change to 1.4.1rc2 (1.4.1 is due in days).
Set USE_LIBTOOL; now the library sort of links (but not really).
Adjust PLIST to be closer.
Still does not work. 
   2009-12-16 12:44:12 by Greg Troxel | Files touched by this commit (1)
Log message:
comment-only change: explain why only 84 is acceptable
   2009-12-16 10:34:03 by Filip Hajny | Files touched by this commit (1)
Log message:
Fixed PGSQL_VERSION checking and provided the correct TEST_TARGET.
   2009-12-15 23:49:25 by Filip Hajny | Files touched by this commit (5) | Imported package
Log message:
Import postgresql84-postgis-1.4.0 as wip/postgresql-postgis.

PostGIS adds support for geographic objects to the PostgreSQL
object-relational database. In effect, PostGIS "spatially enables" the
PostgreSQL server, allowing it to be used as a backend spatial
database for geographic information systems (GIS), much like ESRI's
SDE or Oracle's Spatial extension. PostGIS follows the OpenGIS "Simple
Features Specification for SQL" and has been certified as compliant
with the "Types and Functions" profile.  PostGIS/PostgreSQL includes
the following functionality:

* Simple Features as defined by the OpenGIS Consortium (OGC)
* Support for Well-Known Text and Well-Known Binary
  representations of GIS objects
* Fast spatial indexing using GiST
* Geospatial analysis functions
* PostgreSQL JDBC extension objects corresponding to the
  geometries
* Support for OGC access functions as defined by the Simple
  Features Specification


Next | Query returned 14 messages, browsing 11 to 20 | previous