[pkgsrc/trunk]: pkgsrc/www/php-nextcloud php-nextcloud: Clarify update versio...

[gdt <gdt%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/9c9531689d70
branches:  trunk
changeset: 433928:9c9531689d70
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Mon Jun 08 22:15:42 2020 +0000

description:
php-nextcloud: Clarify update version rule

Be more explicit and give examples.   (This rule is a workaroudn for
an upstream decision, and would not be expected.)  Based on discussion
on pkgsrc-changes with ryoon@.

diffstat:

 www/php-nextcloud/Makefile |  16 ++++++++++------
 1 files changed, 10 insertions(+), 6 deletions(-)

diffs (25 lines):

diff -r 8968285659e6 -r 9c9531689d70 www/php-nextcloud/Makefile
--- a/www/php-nextcloud/Makefile        Mon Jun 08 21:51:59 2020 +0000
+++ b/www/php-nextcloud/Makefile        Mon Jun 08 22:15:42 2020 +0000
@@ -1,11 +1,15 @@
-# $NetBSD: Makefile,v 1.37 2020/06/08 13:12:16 ryoon Exp $
+# $NetBSD: Makefile,v 1.38 2020/06/08 22:15:42 gdt Exp $
 #
 
-# Please make sure not to skip major releases in pkgsrc-current
-# and previous and latest pkgsrc stable branches.
-# Specifically you must ensure that pkgsrc stable branch users can
-# update their www/php-nextcloud in previous branch to current
-# branch without skipping major release.
+# The nextcloud update process only works from one version to the
+# next; one cannot update e.g from 16 to 18.  It is a requirement for
+# stable branch users, if they update every stable branch, to have
+# automatic updates work.  Therefore a major update can only be
+# committed to pkgsrc-current if it is one higher than the major
+# version in the previous stable branch.  As an example, if 2020Q1
+# contained 18.0.2, then during April to June it is ok to update to
+# later 18.x.y, to 19.0.0, and to later 19.x.y, but it is not ok to
+# update to 20.
 DISTNAME=      nextcloud-19.0.0
 PKGNAME=       ${PHP_PKG_PREFIX}-${DISTNAME}
 CATEGORIES=    www