summaryrefslogtreecommitdiff
path: root/devel/subversion/Makefile.version
diff options
context:
space:
mode:
authorgdt <gdt>2009-06-01 18:56:08 +0000
committergdt <gdt>2009-06-01 18:56:08 +0000
commitb9ccb66807f430ecce69a1b0355bec668f5e9cec (patch)
tree43ff9920ce7ea511974bbfa84c982137f7e4bf9f /devel/subversion/Makefile.version
parent4094778cf6f99e9d95a45c2bab96272334de9194 (diff)
downloadpkgsrc-b9ccb66807f430ecce69a1b0355bec668f5e9cec.tar.gz
Explain the scheme to update build-outputs.mk when the svn version changes.
Diffstat (limited to 'devel/subversion/Makefile.version')
-rw-r--r--devel/subversion/Makefile.version12
1 files changed, 7 insertions, 5 deletions
diff --git a/devel/subversion/Makefile.version b/devel/subversion/Makefile.version
index a97cb6ee46a..12141afee63 100644
--- a/devel/subversion/Makefile.version
+++ b/devel/subversion/Makefile.version
@@ -1,9 +1,11 @@
-# $NetBSD: Makefile.version,v 1.49 2009/05/30 00:16:47 gdt Exp $
+# $NetBSD: Makefile.version,v 1.50 2009/06/01 18:56:08 gdt Exp $
+
+# When updating subversion, all packages are updated at the same time
+# to have a consistent set of packages. A particularly tricky aspect
+# is our interaction with the svn build system. See the make target
+# "svn-build-outputs-hack" in devel/subversion-base/Makefile when
+# changing the version.
.if !defined(SVNVER)
-# As of 2009-03-22 gdt@NetBSD.org knows 1.6.0 is out, but is
-# intentionally waiting until post-2009Q1 and until there is enough
-# experience with 1.6.0 before subjecting pkgsrc users to it. Update
-# will probably come mid to late April; comments welcome.
SVNVER= 1.6.2
.endif