upgrade to Pine 4.43

This commit is contained in:
brad 2001-12-01 23:22:58 +00:00
parent 8c34d8eee2
commit 293ea6d6ea
4 changed files with 42 additions and 40 deletions

View File

@ -1,16 +1,16 @@
# $OpenBSD: Makefile,v 1.38 2001/11/22 20:29:20 brad Exp $
# $OpenBSD: Makefile,v 1.39 2001/12/01 23:22:58 brad Exp $
COMMENT= "Program for Internet E-mail and News, with pico"
COMMENT-pico= "small text editor"
COMMENT-pine= "Program for Internet E-mail and News, without pico"
VERSION= 4.42
VERSION= 4.43
PICO_VERSION= 4.2
DISTNAME= pine${VERSION}
PKGNAME= pine+pico-${VERSION}
FULLPKGNAME-pico=pico-${PICO_VERSION}
PKGNAME-pine= pine-${VERSION}
NEED_VERSION= 1.489
NEED_VERSION= 1.500
MASTER_SITES= ftp://ftp.cac.washington.edu/pine/ \
ftp://ftp.sunet.se/pub/unix/mail/pine/
@ -23,6 +23,8 @@ PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= No
PERMIT_DISTFILES_FTP= Yes
NO_REGRESS= Yes
FLAVORS= ldap
FLAVOR?=

View File

@ -1,3 +1,3 @@
MD5 (pine4.42.tar.gz) = a49914a2ca7303285a03e82a8fd9633f
RMD160 (pine4.42.tar.gz) = d9ec636c4914632be3e5c2d890c0e5537325b3bb
SHA1 (pine4.42.tar.gz) = c87eb1e50db21cd7de50a1e0949a56780ef9fe33
MD5 (pine4.43.tar.gz) = 9395df6346b9c0748a93163df83e6150
RMD160 (pine4.43.tar.gz) = 3160888b35779c279e75226f20e8714c7a4fe5ec
SHA1 (pine4.43.tar.gz) = 733bc7797cf8de9f5d5cfd7aab7e4a7dc2127f79

View File

@ -1,7 +1,7 @@
$OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
--- doc/tech-notes.txt.orig Fri Nov 16 14:23:46 2001
+++ doc/tech-notes.txt Sat Nov 17 21:46:12 2001
@@ -328,14 +328,14 @@ SMTP and Sendmail
$OpenBSD: patch-doc_tech-notes.txt,v 1.6 2001/12/01 23:22:59 brad Exp $
--- doc/tech-notes.txt.orig Wed Nov 28 16:21:55 2001
+++ doc/tech-notes.txt Sat Dec 1 14:46:22 2001
@@ -323,14 +323,14 @@ SMTP and Sendmail
sendmail-path, smtp-server, and compile-time options. The first
MTA specified in the following list is used:
@ -20,7 +20,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
9. DF_SENDMAIL_PATH defined at compile time.
10. SENDMAIL and SENDMAILFLAGS defined at compile time.
@@ -658,20 +658,20 @@ Compile-time Options
@@ -654,20 +654,20 @@ Compile-time Options
SENDMAIL
SENDMAILFLAGS
Sets the name and flags for the local program that will be
@ -44,7 +44,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
There are a couple of more obscure options which are in the source
code because a few people have asked for them or because we changed
@@ -865,24 +865,24 @@ Installing Pine and Pico on UNIX Platfor
@@ -861,24 +861,24 @@ Installing Pine and Pico on UNIX Platfor
Installing _Pine_ and _Pico_ is remarkably simple. You take the
program files which you have just transferred or built and you move
them to the correct directory on your system. Most often the binaries
@ -84,7 +84,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
_________________________________________________________________
Installing PC-Pine
@@ -957,13 +957,14 @@ Installing IMAPd
@@ -953,13 +953,14 @@ Installing IMAPd
When the _Pine_ distribution is built on a UNIX system, the IMAP
server binary, imapd, is compiled. Installing imapd requires placing
@ -102,7 +102,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
The /etc/inetd.conf file entry may vary on different versions of UNIX.
Some have a slightly different set of fields. Also the pathname in
@@ -992,11 +993,11 @@ Support Files and Environment Variables:
@@ -988,11 +989,11 @@ Support Files and Environment Variables:
This section lists the various files which _Pine_ uses which are not
email folders. All of these are the default names of files, they may
vary based on _Pine_'s configuration.
@ -117,7 +117,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
Local pointer to system administrator.
~/.pinerc
Personal configuration file for each user.
@@ -1212,10 +1213,10 @@ Pine
@@ -1208,10 +1209,10 @@ Pine
Configuration: Prints a sample system configuration file to the
screen or standard output. To generate an initial system
configuration file, execute
@ -130,7 +130,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
A system configuration file is not required.
-convert_sigs _-p pinerc_
Convert signatures contained in signature files into literal
@@ -1322,9 +1323,9 @@ Pine
@@ -1318,9 +1319,9 @@ Pine
configuration folder.
-P _pinerc_
Uses the named file as the system wide configuration file
@ -140,9 +140,9 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
+ instead of _/etc/pine.conf_ on UNIX, or nothing on _PC-Pine_.
+ Pinerc may be either a local file or a remote configuration
+ folder.
-pinerc _file_
Output fresh pinerc configuration to _file_, preserving the
settings of variables that the user has made. Use _file_ set to
-passfile _passfile_
_PC-Pine_ only. This tells _PC-Pine_ what file should be used
as the password file. This should be a fully-qualified
@@ -1513,8 +1514,8 @@ Pine Configuration
configuration. In most cases, the compiled-in preferences will suit
users and administrators just fine. When running _Pine_ on a UNIX
@ -186,7 +186,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
exist. If it doesn't, then the final path and file must exist.
Note that the last entry is a DOS/Windows path. This is one way
to support _Pine_ running on more than one architecture with
@@ -6860,10 +6861,10 @@ Configuration Inheritance
@@ -6884,10 +6885,10 @@ Configuration Inheritance
5. the system-wide _fixed_ configuration file (Unix _Pine_ only)
The fixed configuration file is normally
@ -199,7 +199,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
_PC-Pine_. For _PC-Pine_, if the environment variable _$PINECONF_ is
set, that is used for the system-wide configuration. This location can
be set or changed on the command line with the -P flag. The
@@ -7017,17 +7018,16 @@ SMTP Servers
@@ -7041,17 +7042,16 @@ SMTP Servers
* A program that implements the SMTP or ESMTP protocol via stdio.
* An entry in /etc/services for the alternate service.
* An entry in /etc/inetd.conf for the alternate service.
@ -221,7 +221,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
In DOS and OS/2, _Pine_ looks in the same directory as the PINERC file
and the same dir as PINE.EXE. This is similar to the UNIX situation
@@ -8215,7 +8215,7 @@ Printers and Printing
@@ -8239,7 +8239,7 @@ Printers and Printing
The second selection is the standard UNIX print command. The default
is _lpr_, but it can be changed on a system basis to anything so
@ -230,7 +230,7 @@ $OpenBSD: patch-doc_tech-notes.txt,v 1.5 2001/11/19 02:01:58 brad Exp $
The third selection is the user's personal choice for a UNIX print
command. The text to be printed is piped into the command. _Enscript_
@@ -8669,9 +8669,9 @@ Test Checklist
@@ -8693,9 +8693,9 @@ Test Checklist
Error messages for incorrect terminal types (try "foo" and
"vt52")
___

View File

@ -1,7 +1,7 @@
$OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
--- pine/pine.hlp.orig Tue Nov 20 18:59:55 2001
+++ pine/pine.hlp Thu Nov 22 15:23:43 2001
@@ -580,9 +580,9 @@ Unix Pine:
$OpenBSD: patch-pine_pine.hlp,v 1.8 2001/12/01 23:22:59 brad Exp $
--- pine/pine.hlp.orig Wed Nov 28 13:07:27 2001
+++ pine/pine.hlp Sat Dec 1 14:40:03 2001
@@ -596,9 +596,9 @@ Unix Pine:
executable <Unix search path>/pine
persnl cfg ~/.pinerc
except cfg ~/.pinercex
@ -14,7 +14,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
interrupted ~/.pine-interrupted-mail
debug ~/.pine-debugN
@@ -594,8 +594,7 @@ Unix Pine:
@@ -610,8 +610,7 @@ Unix Pine:
postponed# ~/mail/postponed-msgs
sentmail# ~/mail/sent-mail
mailcap# ~/.mailcap + /etc/mailcap
@ -24,7 +24,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
news-spool varies across Unix flavors, e.g. /usr/spool/news or /var/news
active-news varies across Unix flavors, e.g. /usr/lib/news/active
@@ -1053,9 +1052,9 @@ contact email address may have been set
@@ -1069,9 +1068,9 @@ contact email address may have been set
this link now to send a message to it:<BR>
<A HREF="X-Pine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
<!--chtml endif-->
@ -36,7 +36,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
<HR WIDTH="75%">
<!--chtml endif-->
<P>
@@ -1143,7 +1142,7 @@ To Exit this screen and continue your Pi
@@ -1159,7 +1158,7 @@ To Exit this screen and continue your Pi
<OL>
<LI> <A HREF="#intro">Introduction</A>
<LI> <A HREF="#pine_help">Pine Help</A>
@ -45,7 +45,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
<LI> <A HREF="#local_support">Local Support Contacts</A>
<!--chtml endif-->
<LI> <A HREF="#giving_cmds">Giving Commands in Pine</A>
@@ -1254,9 +1253,9 @@ copy of Pine you are using has been prop
@@ -1270,9 +1269,9 @@ copy of Pine you are using has been prop
at your site.)
@ -57,7 +57,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
<!--chtml endif-->
<H2><A NAME="giving_cmds">Giving Commands in Pine</A></H2>
@@ -1936,7 +1935,7 @@ screen or standard output. To generate a
@@ -1952,7 +1951,7 @@ screen or standard output. To generate a
file, execute
<PRE><CODE>
@ -66,7 +66,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
</CODE></PRE>
<P>
@@ -1944,7 +1943,7 @@ To generate a system configuration file
@@ -1960,7 +1959,7 @@ To generate a system configuration file
system configuration file, execute
<PRE><CODE>
@ -75,7 +75,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
</CODE></PRE>
<P>
A system configuration file is not required.
@@ -2096,7 +2095,7 @@ Pinerc may be either a local file or a r
@@ -2112,7 +2111,7 @@ Pinerc may be either a local file or a r
<DT> -P <EM>pinerc</EM>
<DD> Uses the named file as the system wide configuration file instead of
@ -84,7 +84,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
Pinerc may be either a local file or a remote configuration folder.
<P>
@@ -2797,10 +2796,10 @@ In increasing order of precedence they a
@@ -2820,10 +2819,10 @@ In increasing order of precedence they a
</OL>
<P>
The fixed configuration file is normally
@ -97,7 +97,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
set for PC-Pine.
For PC-Pine, if the environment variable <EM>$PINECONF</EM> is set, that
is used for the system-wide configuration.
@@ -14144,7 +14143,7 @@ a semi-colon (;) under Windows; for exam
@@ -14167,7 +14166,7 @@ a semi-colon (;) under Windows; for exam
</PRE>
<!--chtml else-->
a colon (:) under UNIX; for example:<PRE>
@ -106,7 +106,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
</PRE>
<!--chtml endif-->
<P><UL>
@@ -16748,7 +16747,7 @@ the fourth is for the connection method
@@ -16771,7 +16770,7 @@ the fourth is for the connection method
<H1>OPTION: ssh-path</H1>
Sets the name of the command used to open a UNIX secure shell
@ -115,7 +115,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
<P>
<UL>
<LI><A HREF="h_finding_help">Finding more information and requesting help</A>
@@ -17527,7 +17526,7 @@ argument (see the &quot;lynx&quot; examp
@@ -17550,7 +17549,7 @@ argument (see the &quot;lynx&quot; examp
So, here are some example entries:
<PRE>
url-viewers = _TEST(&quot;test -n '$&#123;DISPLAY}'&quot;)_ /usr/local/bin/netscape
@ -124,7 +124,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
C:&#92;BIN&#92;NETSCAPE.BAT
</PRE>
<P>
@@ -17535,7 +17534,7 @@ This example shows that for the first vi
@@ -17558,7 +17557,7 @@ This example shows that for the first vi
the environment variable &quot;DISPLAY&quot; must be defined. If it
is, then the path and file &quot;/usr/local/bin/netscape&quot; must exist.
If neither condition is met,
@ -133,7 +133,7 @@ $OpenBSD: patch-pine_pine.hlp,v 1.7 2001/11/22 20:29:20 brad Exp $
If it does, then the &quot;_URL_&quot; token is replaced by the selected URL.
If the path to &quot;lynx&quot; is invalid,
then the final path and file C:&#92;BIN&#92;NETSCAPE.BAT must exist.
@@ -17631,7 +17630,7 @@ because of its length, but should all ap
@@ -17654,7 +17653,7 @@ because of its length, but should all ap
url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ &quot;/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &amp;&quot;<BR>
_TEST(&quot;test -n '$&#123;DISPLAY}'&quot;)_ &quot;/usr/local/bin/netscape &amp;&quot;<BR>