Christopher Nielsen

Tested locally on 10.15, and there are link failures related to Boost: Details ``` Undefined symbols for architecture x86_64: "boost::filesystem::detail::directory_iterator_construct(boost::filesystem::directory_iterator&, boost::filesystem::path const&, unsigned int, boost::system::error_code*)", referenced from: boost::filesystem::directory_iterator::directory_iterator(boost::filesystem::path const&, boost::filesystem::directory_options)...

> Tested locally on 10.15, and there are link failures related to Boost: > [...] Using a newer version of Boost solves that problem. The remaining issue is a link...

NOTE: PR https://github.com/macports/macports-ports/pull/15075 will need to be merged first, as `vigra` doesn't currently support Python 3.10.

Rebased against master, fixing merge conflicts. The only known remaining issue, is the link error for `_Gestalt`. @MarcusCalhoun-Lopez / Anyone, what am I missing...?

> > The only known remaining issue, is the link error for `_Gestalt`. @MarcusCalhoun-Lopez / Anyone, what am I missing...? > > @mascguy: it seems to pass in the CI...

And thank you so much for the contribution @bal-agates!

> One mistake I made was forking macports-ports to my GitHub and then working under master. I should have made a branch on my fork for these changes. Yep, that's...

As for your choice to use separate `post-patch` blocks, one for each associated patch: That approach is just as valid - and in some ways, arguably better - than grouping...

Given that there are a few outdated GNOME ports that depend on this, I'd like to run some additional tests first. So let's hold on this, as well as https://github.com/macports/macports-ports/pull/15549

Tested both `duktape` and `policykit` on a few older macOS releases - 10.7, 10.9, 10.11, and 10.12 - and looks good. Merging both.