Are there any objections to this in its current state?

Remove DBD::mysql again

Sync up with the tree again

Patch out the DBD::mysql and vim-common reqs by removing the version check
functionality which is also an information disclosure vulnerability.

Sync with latest commit

Perl runtime dependency no longer needed.

Add sysutils/beats with patch to fix build

In D16352#350399, @1983-01-06_gmx.net wrote:

So I ran the snippet which perfoms openssl verify against company-internal CAs and I think that this might not really work. Here is our certificate listing. I wrote a simple Java tool which traverses the HTML code, downloads the certs in the physical order and writes them into a combined PEM file.

csplit(1) does not work well here. I'd like someone to prove me wrong if I'm misunderstanding how to use it.

Use sed and split

most concerns addressed except csplit which I need to do some more testing with.

Address all raised concerns except the use of csplit(1) which needs further testing

Fix inconsistency with update-ca-trust: files should be in a subdir named "anchors"

Fix error output to stderr

Now include Java support.

These issues have now been addressed. I have two remaining tasks:

Update ca-merge to address identified concerns

In D16352#347099, @romain wrote:

Looks great!

Besides the in-line comments, maybe it's work considering setting $PATH to some well-known value / use full path of commands to be less sensitive to the user's environment?

Use @sample for cert.pem. We will install the ca-root-nss.crt here, but the cert.pem will
get changed by ca-merge. This is cleaner and leaves us with no strange packaging issues.

pinging on this so we don't forget about it

LGTM

Let me fire off a build against CURRENT as a sanity check (this might also fix the breakage there)

Restoring patches and bumping PORTREVISION for dbn exp-run

For the record, I found a bug related to HTTP headers with my apps that I was able to reproduce with Mono 5.10, so my apps that were "failing" with 5.12 might not have been a 5.12 issue but something else in the 5.x train that caused it. I'd rather we push this out the barn door before 2018Q3 and then we can look at 5.12 in ports again. It should be much easier to upgrade now.

Let's land this

More changes as suggested by dbn