Hi ports@, Here is a diff to update picocom to 3.1.
Notable changes: - Switch to using GitHub - Drop the patch for the old manpage - Sync DESCR with the actual manpage As discussed with him, remove Kyle Isom from MAINTAINER (ENOTIME). Comments? OK? Index: Makefile =================================================================== RCS file: /cvs/ports/comms/picocom/Makefile,v retrieving revision 1.7 diff -u -p -r1.7 Makefile --- Makefile 1 Oct 2016 11:54:14 -0000 1.7 +++ Makefile 11 Jul 2018 16:33:22 -0000 @@ -2,28 +2,24 @@ COMMENT = minimal dumb-terminal emulation program -DISTNAME = picocom-1.7 -REVISION = 0 -CATEGORIES = comms +GH_ACCOUNT = npat-efault +GH_PROJECT = picocom +GH_TAGNAME = 3.1 -HOMEPAGE = https://github.com/npat-efault/picocom -MAINTAINER = Kyle Isom <[email protected]> +CATEGORIES = comms # GPLv2+ PERMIT_PACKAGE_CDROM = Yes WANTLIB += c -MASTER_SITES = ${MASTER_SITE_GOOGLECODE:=picocom/} - MAKE_FLAGS = CC="${CC}" CFLAGS="${CFLAGS}" MAKE_ENV = LDFLAGS="${LDFLAGS}" NO_TEST = Yes do-install: - ${INSTALL_DATA} ${WRKSRC}/picocom.8 ${PREFIX}/man/man8/picocom.8 + ${INSTALL_DATA} ${WRKSRC}/picocom.1 ${PREFIX}/man/man1/picocom.1 ${INSTALL_PROGRAM} ${WRKDIST}/picocom ${PREFIX}/bin/picocom - .include <bsd.port.mk> Index: distinfo =================================================================== RCS file: /cvs/ports/comms/picocom/distinfo,v retrieving revision 1.2 diff -u -p -r1.2 distinfo --- distinfo 23 Oct 2013 03:22:02 -0000 1.2 +++ distinfo 11 Jul 2018 16:33:22 -0000 @@ -1,2 +1,2 @@ -SHA256 (picocom-1.7.tar.gz) = 0PMcj3ohWnaSLTDIGlK5ojSMieAqhJNVFwArO8LBEp4= -SIZE (picocom-1.7.tar.gz) = 42857 +SHA256 (picocom-3.1.tar.gz) = 5nYcqTL/xtCb1rEf8Bi9r3Cyh85RizKC0p4CcOiEILs= +SIZE (picocom-3.1.tar.gz) = 121686 Index: patches/patch-Makefile =================================================================== RCS file: /cvs/ports/comms/picocom/patches/patch-Makefile,v retrieving revision 1.2 diff -u -p -r1.2 patch-Makefile --- patches/patch-Makefile 23 Oct 2013 03:22:02 -0000 1.2 +++ patches/patch-Makefile 11 Jul 2018 16:33:22 -0000 @@ -1,25 +1,14 @@ -$OpenBSD: patch-Makefile,v 1.2 2013/10/23 03:22:02 lteo Exp $ +$OpenBSD$ ---- Makefile.orig Fri Sep 13 19:18:11 2013 -+++ Makefile Fri Sep 13 19:22:09 2013 -@@ -5,16 +5,17 @@ UUCP_LOCK_DIR=/var/lock +Index: Makefile +--- Makefile.orig ++++ Makefile +@@ -18,7 +18,7 @@ TTY_Q_SZ = 0 + CPPFLAGS += -DTTY_Q_SZ=$(TTY_Q_SZ) - # CC = gcc - CPPFLAGS=-DVERSION_STR=\"$(VERSION)\" \ -- -DUUCP_LOCK_DIR=\"$(UUCP_LOCK_DIR)\" \ -- -DHIGH_BAUD -+ -DUUCP_LOCK_DIR=\"$(UUCP_LOCK_DIR)\" - CFLAGS = -Wall -g + ## Comment this out to disable high-baudrate support +-CPPFLAGS += -DHIGH_BAUD ++#CPPFLAGS += -DHIGH_BAUD - # LD = gcc - LDFLAGS = -g - LDLIBS = - -+all: picocom -+ - picocom : picocom.o term.o --# $(LD) $(LDFLAGS) -o $@ $+ $(LDLIBS) -+ $(CC) $(LDFLAGS) -o $@ picocom.o term.o $(LDLIBS) - - picocom.o : picocom.c term.h - term.o : term.c term.h + ## Normally you should NOT enable both: UUCP-style and flock(2) + ## locking. Index: patches/patch-picocom_8 =================================================================== RCS file: patches/patch-picocom_8 diff -N patches/patch-picocom_8 --- patches/patch-picocom_8 23 Oct 2013 03:22:02 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,26 +0,0 @@ -$OpenBSD: patch-picocom_8,v 1.1 2013/10/23 03:22:02 lteo Exp $ - ---- picocom.8.orig Tue Feb 21 09:53:42 2012 -+++ picocom.8 Sun Sep 15 22:34:20 2013 -@@ -123,8 +123,8 @@ picocom --send-cmd "sz -vv" --receive-cmd "rz -vv" - .br - .sp 0.6v - During the picocom session, if you key the "send" or "receive" commands (e.g. by pressing C-a, C-s, or C-a, C-r) you will be prompted for a filename. At this prompt you can enter one or more file-names, and any additional arguments to the transmission or reception program. After that, picocom will start the the external program as specified by the "--send-cmd", or "--receive-cmd" option, and with any filenames and additional arguments you may have supplied. The standard input and output of the external program will be connected to the serial port. The standard error of the external program will be connected to the terminal which---while the program is running---will revert to canonical mode. Pressing 'C-c' while the external program is running will prematurely terminate it, and return control to --.B picocom --. Pressing 'C-c' at any other time, has no special effect; the character is normally passed to the serial port. -+.BR picocom . -+Pressing 'C-c' at any other time, has no special effect; the character is normally passed to the serial port. - .br - .sp 0.6v - .SH INPUT, OUTPUT, AND ECHO MAPPING -@@ -227,8 +227,8 @@ to already-connected modems, or already configured por - If given, - .B picocom - will not *reset* the serial port when exiting. It will just close the filedes and do nothing more. This is useful, for example, for leaving modems connected when exiting --.B picocom --. Regardless whether the "--noreset" option is given the user can exit -+.BR picocom . -+Regardless whether the "--noreset" option is given the user can exit - .B picocom - using the "Quit" command (instead of "Exit"), which never resets the serial port. If "--noreset" is given then "Quit" and "Exit" behave essentially the same. - .TP 3 Index: pkg/DESCR =================================================================== RCS file: /cvs/ports/comms/picocom/pkg/DESCR,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 DESCR --- pkg/DESCR 8 Jul 2012 18:19:18 -0000 1.1.1.1 +++ pkg/DESCR 11 Jul 2018 16:33:22 -0000 @@ -1,13 +1,9 @@ As its name suggests, picocom is a minimal dumb-terminal emulation -program. It is, in principle, very much like minicom, only it's pico +program. It is, in principle, very much like minicom, only it's pico instead of mini! -Picocom was designed to serve as a simple, manual, modem configuration, +It was designed to serve as a simple, manual, modem configuration, testing, and debugging tool. It has also served (quite well) as a -low-tech "terminal-window" to allow operator intervention in PPP -connection scripts (something like the ms-windows "open terminal window -before / after dialing" feature). It could also prove useful in many -other similar tasks. - -Picocom is ideal for embedded systems since its memory footprint is -minimal (less than 20K, when stripped). +low-tech serial communications program to allow access to all types of +devices that provide serial consoles. It could also prove useful in +many other similar tasks. Index: pkg/PLIST =================================================================== RCS file: /cvs/ports/comms/picocom/pkg/PLIST,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 PLIST --- pkg/PLIST 8 Jul 2012 18:19:18 -0000 1.1.1.1 +++ pkg/PLIST 11 Jul 2018 16:33:23 -0000 @@ -1,3 +1,3 @@ @comment $OpenBSD: PLIST,v 1.1.1.1 2012/07/08 18:19:18 lteo Exp $ @bin bin/picocom -@man man/man8/picocom.8 +@man man/man1/picocom.1
