Turns out I made a bad assumption and the update didn't go through
a bulk. There's a bunch of failures on exopi and I'm not sure I have
the time to fix them today. Sorry folks.
knot's configure script tries to detect liblmdb.so and lmdb.h, if it
can't find them it automatically adds /usr/local/{include,lib}
to the search paths then rechecks. This works well on clang archs. On
gcc archs ports-gcc automatically adds /usr/local/lib to the ld(1)
search path so detection of liblmdb.so works out of the box, but lmdb.h
can't be found since /usr/local/include hasn't been added to CPPFLAGS,
triggering a fatal error. sigh
Perl 5.28.1 no longer defines I_STDLIB and I_STRING in its config.h.
Unconditionally include the correct headers to avoid miscompilation
due to missing prototypes.
Sort according to Makefile.template.
Take maintainer.
OK sthen@
Switch to cmake, enable i18n support and unit tests.
Also:
- don't install libxmp.a from the Adobe XMP SDK, to avoid confusion with
audio/libxmp
- don't provide the new Exiv2::getProcessPath() function. Not portable,
doesn't work on OpenBSD, and shouldn't be exposed in the API of
a graphics library. Instead, define a macro with CMake to help runtime
find gettext files.
Sample executables are now built and installed, not sure if all of them
are very useful.
From danj@ with input from sthen@, ajacoutot@ and me, tested in a bulk
by ajacoutot@
OK giovanni@
Comment:
iterative DMARC validation for mails
Description:
This module can be used to validate mails against DMARC policies
like specified in RFC 7208. The main difference to Mail::DMARC is
that it does no blocking operations. Instead it implements a state
machine where user input is fed into and instructions what the
machine wants is returned. The state machine only wants the data
from the mail and the result of specific DNS lookups. With each
new data fed into the machine it will provide new information what
it needs next, until it finally has enough input and returns the
final result. Because of this design the DMARC policy validation
can be easily integrated into event-driven programs or coupled with
a specific DNS resolver.
