SF.net SVN: gar:[22367] csw/mgar/pkg/pg-ip4r/trunk/Makefile

[guengel at users.sourceforge.net]

Revision: 22367
          http://gar.svn.sourceforge.net/gar/?rev=22367&view=rev
Author:   guengel
Date:     2013-11-03 20:11:02 +0000 (Sun, 03 Nov 2013)
Log Message:
-----------
pg-ip4r/trunk: Added comments.

Modified Paths:
--------------
    csw/mgar/pkg/pg-ip4r/trunk/Makefile

Modified: csw/mgar/pkg/pg-ip4r/trunk/Makefile
===================================================================
--- csw/mgar/pkg/pg-ip4r/trunk/Makefile	2013-11-03 18:51:43 UTC (rev 22366)
+++ csw/mgar/pkg/pg-ip4r/trunk/Makefile	2013-11-03 20:11:02 UTC (rev 22367)
@@ -1,6 +1,31 @@
 # $Id$
-# TODO (release-critical prefixed with !, non release-critical with *)
 #
+# What's going on in this recipe?
+# -------------------------------
+#
+# This recipe uses modulation to build ip4r in the sources of each
+# PostgreSQL version separately.
+#
+# The sources of each PostgreSQL version supported by OpenCSW are
+# extracted and configured (i.e. ./configure is called with the same
+# arguments used as if building PostgreSQL), and ip4r is copied to the
+# contrib directory. Then, make and 'make install' are called only in
+# contrib/ip4r.
+#
+# Further, PostgreSQL 8.4 to 9.0 use ip4r without support for
+# extensions, which were introduced in 9.1. So 9.1+ use ip4r with
+# support for extensions.
+#
+#
+# Why doing it the hard way?
+# --------------------------
+#
+# Currently, OpenCSW PostgreSQL provides development files only for
+# the most recent PostgreSQL version. Though it might be possible to
+# build ip4r using the latest development files, and provide the
+# resulting library for earlier versions, I stayed away from that
+# approach, in order to avoid any possible incompatibilities.
+# 
 NAME = pg-ip4r
 VERSION = 2.0
 GARTYPE = v2

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.