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/
===> The following configuration options are available for librfc822-1.2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove expired ports:
Adjusted for ports rescued since r534032
2020-05-05 audio/festvox-czech: Broken for more than 6 months
2020-05-05 audio/gkrellmvolume2: Broken for more than 6 months
2020-05-05 audio/mixmos: Broken for more than 6 months
2020-05-05 audio/mma: Broken for more than 6 months
2020-05-05 audio/pd-cyclone: Broken for more than 6 months
2020-05-05 audio/shorten: Broken for more than 6 months
2020-05-05 audio/taglib-sharp: Broken for more than 6 months
2020-05-05 audio/xhippo: Broken for more than 6 months
2020-05-05 biology/consed: Broken for more than 6 months
2020-05-05 biology/plinkseq: Broken for more than 6 months
2020-05-05 biology/seqtools: Broken for more than 6 months
(Only the first 15 lines of the commit message are shown above )
Remove indefinite articles and trailing periods from COMMENT, plus minor
COMMENT typos and surrounding whitespace fixes. A few Makefiles where not
included as they contain Latin-1 characters that break the Phabricator
workflow. Category M.
CR: D306
Approved by: portmgr (bapt)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
- Unbreak on -CURRENT (patch added)
- Add devel as a secondary category
- Use INSTALL_DATA instead of CP to install documentation
- Only install the .txt/.html/.pdf files, skip supporting files
- Bump PORTREVISION due to changed package
PR: 50921
Submitted by: Sergei Kolobov <sergei@kolobov.com>