Date: Thu, 30 Sep 1999 11:12:56 -0400 (EDT) From: kbyanc@posi.net To: FreeBSD-gnats-submit@freebsd.org Subject: ports/14054: new port: mail/mmencode Message-ID: <199909301512.LAA61424@kronos.alcnet.com>
next in thread | raw e-mail | index | archive | help
>Number: 14054 >Category: ports >Synopsis: new port: mail/mmencode >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Sep 30 08:20:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Kelly Yancey >Release: FreeBSD 3.2-STABLE i386 >Organization: >Environment: >Description: Below is a port of the mmencode program (actually a component of metamail) I created a separate port for just the mmencode program because: a) metamail requires X, with mmencode I can process MIME-encoded files without having to have X installed b) I currently have 1 port (bgrab), non-X, which requires mmencode; creating a dependency on metamail in order to get mmencode installed would also install X (bad). c) it is useful in and of itself Kelly ~kbyanc@posi.net~ # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # mmencode # mmencode/pkg # mmencode/pkg/PLIST # mmencode/pkg/COMMENT # mmencode/pkg/DESCR # mmencode/files # mmencode/files/md5 # mmencode/Makefile # mmencode/patches # mmencode/patches/patch-aa # echo c - mmencode mkdir -p mmencode > /dev/null 2>&1 echo c - mmencode/pkg mkdir -p mmencode/pkg > /dev/null 2>&1 echo x - mmencode/pkg/PLIST sed 's/^X//' >mmencode/pkg/PLIST << 'END-of-mmencode/pkg/PLIST' Xbin/mmencode Xbin/mimencode X END-of-mmencode/pkg/PLIST echo x - mmencode/pkg/COMMENT sed 's/^X//' >mmencode/pkg/COMMENT << 'END-of-mmencode/pkg/COMMENT' XTranslate to and from mail-oriented encoding formats END-of-mmencode/pkg/COMMENT echo x - mmencode/pkg/DESCR sed 's/^X//' >mmencode/pkg/DESCR << 'END-of-mmencode/pkg/DESCR' XFrom the man page: X X The mimencode program simply converts a byte stream into (or out of) one of X the standard mail encoding formats defined by MIME, the proposed standard X for internet multimedia mail formats. Such an encoding is necessary X because binary data cannot be sent through the mail. The encodings under- X stood by mimencode are preferable to the use of the uuencode/uudecode pro- X grams, for use in mail, in several respects that were important to the X authors of MIME. X XMmencode is part of metamail, and can be installed as part of that package. XIt is provided here as an independent package since some programs require Xmmencode only and hence you can avoid having to install the entire metalmail Xpackage when not required. X X -Kelly X ~kbyanc@posi.net~ END-of-mmencode/pkg/DESCR echo c - mmencode/files mkdir -p mmencode/files > /dev/null 2>&1 echo x - mmencode/files/md5 sed 's/^X//' >mmencode/files/md5 << 'END-of-mmencode/files/md5' XMD5 (mm2.7.tar.Z) = fd5617ea87e20d7f2fa839e1d1fede60 END-of-mmencode/files/md5 echo x - mmencode/Makefile sed 's/^X//' >mmencode/Makefile << 'END-of-mmencode/Makefile' X# New ports collection makefile for: mmencode X# Version required: 2.7 X# Date created: 30 September 1999 X# Whom: kbyanc X# X# $FreeBSD$ X# X XDISTNAME= mm2.7 XPKGNAME= mmencode-2.7 X XCATEGORIES= mail XMASTER_SITES= ftp://thumper.bellcore.com/pub/nsb/ XEXTRACT_SUFX= .tar.Z X XMAINTAINER= kbyanc@posi.net X XWRKSRC= ${WRKDIR}/${DISTNAME}/src X XMAN1= mmencode.1 X XALL_TARGET= mmencode X Xdo-build: X cd ${WRKSRC}/metamail && ${MAKE} ${ALL_TARGET} X Xdo-install: X @cd ${WRKSRC}/metamail && ${INSTALL_PROGRAM} mmencode ${PREFIX}/bin X @cd ${WRKSRC}/man && ${CP} mmencode.1 ${PREFIX}/man/man1 X @cd ${PREFIX}/bin && ${LN} -s mmencode mimencode X X.include <bsd.port.mk> END-of-mmencode/Makefile echo c - mmencode/patches mkdir -p mmencode/patches > /dev/null 2>&1 echo x - mmencode/patches/patch-aa sed 's/^X//' >mmencode/patches/patch-aa << 'END-of-mmencode/patches/patch-aa' X--- man/mmencode.1.orig Thu Sep 30 10:50:02 1999 X+++ man/mmencode.1 Thu Sep 30 10:53:37 1999 X@@ -1,44 +1,42 @@ X-.TH MIMENCODE 1 "Release 1" "Bellcore Prototype" X+.TH MMENCODE 1 "Release 1" "Bellcore Prototype" X .SH NAME X-mimencode - Translate to and from mail-oriented encoding formats X+mmencode - Translate to and from mail-oriented encoding formats X X-(Same program also installed as "mmencode".) X+(Same program also installed as "mimencode".) X .SH SYNOPSIS X .ta 8n X-\fBmimencode\fP [-u] [-b] [-q] [-p] [file name] [-o outputfile] X+\fBmmencode\fP [-u] [-b] [-q] [-p] [file name] [-o outputfile] X .br X .SH DESCRIPTION X The X-.I mimencode X-program simply converts a byte stream into (or out of) one of the standard mail encoding formats defined by MIME, the proposed standard for internet multimedia mail formats. Such an encoding is necessary because binary data cannot be sent through the mail. The encodings understood by mimencode are preferable to the use of the uuencode/uudecode programs, for use in mail, in several respects that were important to the authors of MIME. X+.I mmencode X+program simply converts a byte stream into (or out of) one of the standard mail encoding formats defined by MIME, the proposed standard for internet multimedia mail formats. Such an encoding is necessary because binary data cannot be sent through the mail. The encodings understood by mmencode are preferable to the use of the uuencode/uudecode programs, for use in mail, in several respects that were important to the authors of MIME. X X-By default, mimencode reads standard input, and sends a "base64" encoded version of the input to standard output. X+By default, mmencode reads standard input, and sends a "base64" encoded version of the input to standard output. X X-The (really not necessary) "-b" option tells mimencode to use the "base64" encoding. X+The (really not necessary) "-b" option tells mmencode to use the "base64" encoding. X X-The "-q" option tells mimencode to use the "quoted-printable" encoding instead of base64. X+The "-q" option tells mmencode to use the "quoted-printable" encoding instead of base64. X X-The "-u" option tells mimencode to X+The "-u" option tells mmencode to X .I X decode X the standard input rather than encode it. X X-The "-p" option tells mimencode to translate decoded CRLF sequences into the local newline convention during decoding and to do the reverse during encoding. This option is only meaningful when -b (base64 encoding) is in effect. X+The "-p" option tells mmencode to translate decoded CRLF sequences into the local newline convention during decoding and to do the reverse during encoding. This option is only meaningful when -b (base64 encoding) is in effect. X X If a file name argument is given, input is read from that file rather than from standard input. X X The "-o" option, which must be followed by a file name, sends output to the named file rather than to standard output. X .SH RATIONALE X .I X-Mimencode X+Mmencode X is intended to be a replacement for X .I X uuencode X-for mail and news use. The reason is simple: uuencode doesn't work very well in a number of circumstances and ways. In particular, uuencode uses characters that don't translate well across all mail gateways (particularly ASCII <-> EBCDIC gateways). Also, uuencode is not standard -- there are several variants floating around, encoding and decoding things in different and incompatible ways, with no "standard" on which to base an implementation. Finally, uuencode does not generally work well in a pipe, although some variants have been modified to do so. Mimencode implements the encodings which were defined for MIME as uuencode replacements, and should be considerably more robust for email use. X+for mail and news use. The reason is simple: uuencode doesn't work very well in a number of circumstances and ways. In particular, uuencode uses characters that don't translate well across all mail gateways (particularly ASCII <-> EBCDIC gateways). Also, uuencode is not standard -- there are several variants floating around, encoding and decoding things in different and incompatible ways, with no "standard" on which to base an implementation. Finally, uuencode does not generally work well in a pipe, although some variants have been modified to do so. Mmencode implements the encodings which were defined for MIME as uuencode replacements, and should be considerably more robust for email use. X .SH SEE ALSO X metamail(1), mailto(1) X-.SH BUGS X-This program was originally distributed as "mmencode". That name turns out to conflict with a program of the same name that is part of the Slate software from BBN, but totally changing the name to mimencode would create other problems (notably with portability to systems where the left half of file names is limited to 8 characters). Currently, it is being distributed with links under BOTH names. The programs in the distribution that call the program all call it as "mimencode", so the "mmencode" version may be deleted at sites where it causes a problem. (The source files are still named "mmencode" rather than "mimencode".) X .SH COPYRIGHT X Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore) X END-of-mmencode/patches/patch-aa exit >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909301512.LAA61424>