yesterday I bumped the SHARED_LIBS version to enforce updates of sqlite
because some users have a tight check on build vs library version; on
reflection I think it would be simpler to set PKGSPEC so that an extra
step is not needed.
ok/comments?
Index: Makefile
===================================================================
RCS file: /cvs/ports/databases/sqlite3/Makefile,v
retrieving revision 1.100
diff -u -p -r1.100 Makefile
--- Makefile 28 Mar 2019 21:13:47 -0000 1.100
+++ Makefile 29 Mar 2019 10:58:59 -0000
@@ -2,17 +2,12 @@
COMMENT= embedded SQL implementation
+V= 3.27.2
DISTNAME = sqlite-autoconf-3270200
-PKGNAME= sqlite3-3.27.2
+PKGNAME= sqlite3-$V
REVISION= 0
-# XXX needs bumps every time :-
SHARED_LIBS += sqlite3 37.5 # 8.6
-# sqlite suggests that users might like to assert() that library and header
-# versions match, so bumps are needed even if function signatures don't change.
-# ... at the current time the only one noticed is a < check (in subversion)
-# rather than an == check so minor bumps are enough to cope with this, though
-# we may run into others later.
CATEGORIES= databases
@@ -24,6 +19,11 @@ PERMIT_PACKAGE_CDROM= Yes
WANTLIB += c curses m pthread readline z
MASTER_SITES = ${HOMEPAGE}2019/
+
+# enforce updates in dependent ports; sqlite suggests that code using the
+# library asserts that library and header versions are in sync - e.g.
+# subversion and mozilla have a < check, freeradius has an == check.
+PKGSPEC= sqlite3-=$V
CONFIGURE_STYLE= gnu
CONFIGURE_ARGS= --enable-editline \
