Update imap-uw to the latest version (imap-2000).
Update pine4 to the latest version (pine-4.31).
Despite the fact that the new releases of imap-uw and pine are
intended to improve security, the security warnings on the pine
and imap-uw ports have been left intact until they have proven
themselves.
Mike Silbersack <silby@silby.com>. Add a build- and install-time
warning about the probable existence of further remote security
problems, and remove FORBIDDEN.
Submitted by: Mike Silbersack <silby@silby.com>
Parenthetically, no software which uses 4299 sprintf/strcpy/strcat
calls can possibly be safe - I don't expect to remove this FORBIDDEN
tag any time soon. :-(
Pine has historically built against an internal copy of the c-client library,
however c-client development has progressed beyond what is shipped with pine.
(It would appear that all new development work is being done via UW's imap
server codebase.) This change allows pine to utilize improvements/bugfixes in
the c-client library. In addition, the cclient port builds c-client as a
a shared library. Now, pine links against this shared library. As a result,
pine binaries are approximately 550k smaller. On the other hand, the c-client
library itself is a good 650k. The real benefit here is that c-client may be
shared amongst multiple binaries (i.e. imap-uw, php, and perl scripts using the
p5-Mail-CClient module), thereby potentially reducing the overall disk and
memory usage.
PR: 19731
Submitted by: kbyanc@posi.net
Reviewed by: will
master). This is done by defining a variable "PRE_MK_INCLUDED" in the slave
before including ${MASTERDIR}/Makefile, and have the master check it before
including any necessary macro files.
Makefile.diff - patch to Makefile; gzip additional manpages during
postinstall
file.Makefile.diff - patch to files/Makefile; add install
for new manpages
PLIST.diff - include new manpages in package
1. Make MASTER_SITES entries contain a trailing /. Garrett says that
assuming a '/' seperator between entries in MASTER_SITES and entries
in DISTFILES is a dangerous assumption. This will also be taken
out of bsd.port.mk.
2. General clean-up. Some of these Makefiles were a little grim.
Make sure they're all in sync with the sometimes rapidly changing
bsd.port.mk! :)
3. Some small configuration tweaks to keep them compiling under the
most recent 2.0 - some things seem to have broken along our road
to release.
bring it into line with the others (always clone another port when
starting a new one if you can, folks, it saves work and makes them
look more standard).
Submitted by: jkh
