Thanks for the info, Ryan. That's really interesting that the Boost
powers-that-be don't think such a critical error in boost::beast to not require
a quick rev-bump. They could fix their broken CMake find scripts at the same
time! Grrr
I'm really of mixed mind about patching Boost beyond a
On May 19, 2019, at 10:13, Michael Dickens wrote:
> I'm looking for advice on how to move forward with Boost 1.70.0's CMake find
> scripts: do we just not install them? Or do we patch them via what upstream
> has already done? Or do we just wait for 1.70.1 -- which will contain those
> fixes
We're working on updating Boost to 1.70.0 <
https://github.com/macports/macports-ports/pull/4243 > ... we'd value others
participating, BTW! Thus far many ports work out of the box with it (current
Boost in MacPorts is 1.66.0, so there are some significant bug fixes and API
changes to deal with
