Noticed this update while working on other things. The module adds parsing of Content-Disposition headers plus many other improvements, the port is just a simple update, although I did adjust the DESCR to mention the new header and TEST_DEPENDS are reduced do to the test improvements.
https://metacpan.org/changes/distribution/Email-MIME-ContentType Comments, OK? Index: Makefile =================================================================== RCS file: /cvs/ports/mail/p5-Email-MIME-ContentType/Makefile,v retrieving revision 1.12 diff -u -p -r1.12 Makefile --- Makefile 20 Mar 2016 19:56:45 -0000 1.12 +++ Makefile 8 May 2019 14:32:45 -0000 @@ -1,17 +1,15 @@ # $OpenBSD: Makefile,v 1.12 2016/03/20 19:56:45 naddy Exp $ -COMMENT= parses a MIME Content-Type Header +COMMENT= parse MIME Content-Type or Content-Disposition headers MODULES= cpan PKG_ARCH= * -DISTNAME = Email-MIME-ContentType-1.018 +DISTNAME= Email-MIME-ContentType-1.022 CATEGORIES= mail MAINTAINER= Sam Smith <s...@msmith.net> # GPL PERMIT_PACKAGE_CDROM= Yes - -TEST_DEPENDS= sysutils/p5-Capture-Tiny .include <bsd.port.mk> Index: distinfo =================================================================== RCS file: /cvs/ports/mail/p5-Email-MIME-ContentType/distinfo,v retrieving revision 1.6 diff -u -p -r1.6 distinfo --- distinfo 14 Nov 2015 20:46:10 -0000 1.6 +++ distinfo 8 May 2019 14:32:45 -0000 @@ -1,2 +1,2 @@ -SHA256 (Email-MIME-ContentType-1.018.tar.gz) = dQjNEie48VCkA8pJZYy0oIkoNt2PAf+V8EmVeyq/EPk= -SIZE (Email-MIME-ContentType-1.018.tar.gz) = 17195 +SHA256 (Email-MIME-ContentType-1.022.tar.gz) = mrtygLDaYqhVrlUosU3rlDQahOchrwp+WircNTTsUxA= +SIZE (Email-MIME-ContentType-1.022.tar.gz) = 20365 Index: pkg/DESCR =================================================================== RCS file: /cvs/ports/mail/p5-Email-MIME-ContentType/pkg/DESCR,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 DESCR --- pkg/DESCR 15 Jan 2006 15:24:39 -0000 1.1.1.1 +++ pkg/DESCR 8 May 2019 14:32:45 -0000 @@ -1,2 +1,4 @@ -This module is responsible for parsing email content type -headers according to section 5.1 of RFC 2045. +Parses email content type headers according to section 5.1 of RFC +2045 and also RFC 2231 (Character Set and Parameter Continuations) +as well as email Content-Disposition headers according to RFC 2183 +and RFC 2231.
