Browse files

Adjust comments (only) about shlib versioning.

Upstream says using the C++ API is broken; document the policy and the
list of (broken per geos rules) packages that need a revbump every
time, currently gdal-lib.
  • Loading branch information...
1 parent 330aee1 commit 77ea75d60fc1954dae4b0b152e1b8de95f9278f7 gdt committed Jun 5, 2012
Showing with 17 additions and 8 deletions.
  1. +17 −8 geography/geos/Makefile
@@ -1,17 +1,26 @@
-# $NetBSD: Makefile,v 1.17 2012/06/03 16:05:44 gdt Exp $
+# $NetBSD: Makefile,v 1.18 2012/06/05 23:17:32 gdt Exp $
DISTNAME= geos-3.3.4
CATEGORIES= geography
EXTRACT_SUFX= .tar.bz2
-# NOTE: geos uses -release for versioning lib/, and seems to
-# change the shlib name (not just the version, but the *name*) on
-# every release. If this continues, a recursive revbump is required
-# on every update.
-# This has been reported as a bug to the upstream mailinglist:
+# geos has two libraries:
+# geos_c (C), which follows normal versioning rules
+# geos (C++), which uses -release, and changes on every release
+# According to the geos project, the C++ interface should not be
+# directly used and other packages should not link against it. This
+# is currently underdocumented:
+# Therefore, pkgsrc will perform a recursive revbump when the geos_c
+# shlib version changes, and will generally ignore geos shlib name
+# changes. The following packages incorrectly (from the geos
+# viewpoint) link directly against -lgeos and should be revbumped on
+# every update (and fixed not to use -lgeos):
+# geography/gdail-lib

0 comments on commit 77ea75d

Please sign in to comment.