> -DISTNAME = rancid-2.3.8
> -REVISION = 0
> +DISTNAME = rancid-3.5.1
> +DISTPATCH = 1
> +PKGNAME = ${DISTNAME}pl${DISTPATCH}
Yep, the pl bits ar reasonable.
> @@ -18,21 +19,21 @@ PERMIT_PACKAGE_FTP = Yes
> WANTLIB = c util
>
> MASTER_SITES = ftp://ftp.shrubbery.net/pub/rancid/
> +MASTER_SITES0 = ftp://ftp.shrubbery.net/pub/rancid/
> +
> +PATCHFILES = ${DISTNAME}.p${DISTPATCH}.gz:0
No need for MASTER_SITES0 as it's the same, just remove ":0".
> Index: pkg/MESSAGE
> ===================================================================
> RCS file: pkg/MESSAGE
> diff -N pkg/MESSAGE
> --- /dev/null 1 Jan 1970 00:00:00 -0000
> +++ pkg/MESSAGE 14 Nov 2016 19:38:28 -0000
> @@ -0,0 +1,7 @@
> +If you are upgrading from rancid-<3, please note that router.db field
> +separator has been changed from ':' to ';' to avoid conflict with IPv6
> +addresses. Replace the field separator in router.db files before running
> +rancid.
> +
> +The configuration files location is changed from ${SYSCONFDIR} to
> +${SYSCONFDIR}/rancid.
> Index: pkg/PLIST
> ===================================================================
> RCS file: /cvs/ports/sysutils/rancid/pkg/PLIST,v
> retrieving revision 1.7
> diff -u -p -r1.7 PLIST
> --- pkg/PLIST 8 Jun 2012 13:59:08 -0000 1.7
> +++ pkg/PLIST 14 Nov 2016 19:38:28 -0000
> @@ -1,19 +1,25 @@
> @comment $OpenBSD: PLIST,v 1.7 2012/06/08 13:59:08 pea Exp $
> @conflict par-*
> +@conflict rancid-<3v0
Except for special situations (e.g. what we have in autoconf), an @conflict
on the same port doesn't make sense.
> +@ask-update rancid-<3v0 Make sure router.db files use new fields separator
> before upgrading
I think either MESSAGE *or* @ask-update is enough. ask-update is quite
annoying so I'd rather restrict it for use in special cases (like postgresql,
where <until Jeremy's work goes in> there is significant extra hassle if you
don't dump before the package gets updated) and stick to just MESSAGE.
