pkgsrc-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[pkgsrc/trunk]: pkgsrc/net/unison2.51 net/unison2.51: Adjust comment about ve...



details:   https://anonhg.NetBSD.org/pkgsrc/rev/69b41c0c21fb
branches:  trunk
changeset: 374692:69b41c0c21fb
user:      gdt <gdt%pkgsrc.org@localhost>
date:      Thu Feb 24 13:50:39 2022 +0000

description:
net/unison2.51: Adjust comment about versions

The next version will be 2.52.0, and this will interoperate with 2.51.
That is expected to continue indefinitely.  There is no reason to have
multiple versions again, so say that the next update will move to the
unversioned name.

diffstat:

 net/unison2.51/Makefile |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (18 lines):

diff -r a55f6005e139 -r 69b41c0c21fb net/unison2.51/Makefile
--- a/net/unison2.51/Makefile   Thu Feb 24 13:47:48 2022 +0000
+++ b/net/unison2.51/Makefile   Thu Feb 24 13:50:39 2022 +0000
@@ -1,10 +1,10 @@
-# $NetBSD: Makefile,v 1.37 2022/02/24 13:47:48 gdt Exp $
+# $NetBSD: Makefile,v 1.38 2022/02/24 13:50:39 gdt Exp $
 
 # Currently, 2.51.x is the standard approach, and thus this package
 # produces a "unison-2.51.x" package which installs a "unison" binary.
-# When the next unison branch is released, we will likely again have
-# multiple unison packages, with whichever is the standard approach
-# using the unversioned name.
+# Now, unison no longer has the problem of interoperating within minor
+# verisons, and the update to 2.52 will likely rename this to
+# net/unison, as there is no longer any reason to have old versions.
 DISTNAME=      unison-2.51.5
 #PKGREVISION=  0
 CATEGORIES=    net



Home | Main Index | Thread Index | Old Index