diff options
| -rw-r--r-- | mail/Makefile | 1 | ||||
| -rw-r--r-- | mail/librfc822/Makefile | 24 | ||||
| -rw-r--r-- | mail/librfc822/distinfo | 1 | ||||
| -rw-r--r-- | mail/librfc822/pkg-comment | 1 | ||||
| -rw-r--r-- | mail/librfc822/pkg-descr | 10 | ||||
| -rw-r--r-- | mail/librfc822/pkg-plist | 14 |
6 files changed, 51 insertions, 0 deletions
diff --git a/mail/Makefile b/mail/Makefile index b5984923..9e598b8 100644 --- a/mail/Makefile +++ b/mail/Makefile @@ -81,6 +81,7 @@ SUBDIR += liamail SUBDIR += libesmtp SUBDIR += liboe + SUBDIR += librfc822 SUBDIR += listar SUBDIR += listmanager SUBDIR += lmtp2nntp diff --git a/mail/librfc822/Makefile b/mail/librfc822/Makefile new file mode 100644 index 0000000..7e17928 --- /dev/null +++ b/mail/librfc822/Makefile @@ -0,0 +1,24 @@ +# ex:ts=8 +# Ports collection makefile for: librfc822 +# Date created: Apr 19, 2002 +# Whom: ijliao +# +# $FreeBSD$ +# + +PORTNAME= librfc822 +PORTVERSION= 1.0 +CATEGORIES= mail +MASTER_SITES= http://cryp.to/librfc822/ + +MAINTAINER= ports@FreeBSD.org + +do-install: + ${INSTALL_DATA} ${WRKSRC}/rfc822.hh ${PREFIX}/include + ${INSTALL_DATA} ${WRKSRC}/librfc822.a ${PREFIX}/lib +.if !defined(NOPORTDOCS) + @${MKDIR} ${DOCSDIR} + ${CP} ${WRKSRC}/documentation/* ${DOCSDIR} +.endif + +.include <bsd.port.mk> diff --git a/mail/librfc822/distinfo b/mail/librfc822/distinfo new file mode 100644 index 0000000..9012fb5 --- /dev/null +++ b/mail/librfc822/distinfo @@ -0,0 +1 @@ +MD5 (librfc822-1.0.tar.gz) = 4dca8e2b6fe3ffaabc5f3b9c493e57c6 diff --git a/mail/librfc822/pkg-comment b/mail/librfc822/pkg-comment new file mode 100644 index 0000000..dbf366e --- /dev/null +++ b/mail/librfc822/pkg-comment @@ -0,0 +1 @@ +A complete parser for RFC822 addresses diff --git a/mail/librfc822/pkg-descr b/mail/librfc822/pkg-descr new file mode 100644 index 0000000..1566d74 --- /dev/null +++ b/mail/librfc822/pkg-descr @@ -0,0 +1,10 @@ +librfc822 provides application developers with a complete parser for RFC822 +addresses. Not only can you use the library to verify that RFC822 addresses +are syntactically correct, you can also have an address split up into its +semantic parts, what is needed when deciding where to route an address to, etc. + +What is quite unique is that librfc822 does indeed parse all address types +allowed by the standard. That includes such weird things as "address groups" +or addresses with whitespace and comments throw in. + +WWW: http://cryp.to/librfc822/ diff --git a/mail/librfc822/pkg-plist b/mail/librfc822/pkg-plist new file mode 100644 index 0000000..60d7cce --- /dev/null +++ b/mail/librfc822/pkg-plist @@ -0,0 +1,14 @@ +include/rfc822.hh +lib/librfc822.a +%%PORTDOCS%%share/doc/librfc822/Makefile +%%PORTDOCS%%share/doc/librfc822/index.sgml +%%PORTDOCS%%share/doc/librfc822/peti.css +%%PORTDOCS%%share/doc/librfc822/peti.dsl +%%PORTDOCS%%share/doc/librfc822/purpose.inc +%%PORTDOCS%%share/doc/librfc822/readme.html +%%PORTDOCS%%share/doc/librfc822/readme.sgml +%%PORTDOCS%%share/doc/librfc822/readme.txt +%%PORTDOCS%%share/doc/librfc822/user-manual.html +%%PORTDOCS%%share/doc/librfc822/user-manual.pdf +%%PORTDOCS%%share/doc/librfc822/user-manual.sgml +%%PORTDOCS%%@dirrm share/doc/librfc822 |
