[MacPorts] #50572: boost @1.59.0 Update to to 1.60.0

[MacPorts]

#50572: boost @1.59.0 Update to to 1.60.0
------------------------+--------------------------
  Reporter:  crmoore@…  |      Owner:  ryandesign@…
      Type:  update     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:
      Port:  boost      |
------------------------+--------------------------
Changes (by ryandesign@…):

 * cc: uri@… (added)


Comment:

 Replying to [comment:2 uri@…]:
 > So far in my experience all the boost upgrades (tracking from 1.52) went
 pretty well. Thus there's a good chance that most of the ports depending
 on boost won't need to be changed. (Or am I missing something?)

 Many, even most, prior boost updates have broken some ports. This is
 because the developers of boost do not appear to consider backward
 compatibility a priority and frequently make breaking changes. They also
 do not assign library version numbers, so it is not possible to tell at a
 glance when such breakage has occurred. In the past, I've simply updated
 the boost port, leaving it to the users and maintainers of ports that use
 boost to discover and fix any breakage. This is a bad user experience. So
 before I commit a boost update, I would like to verify that a number of
 popular ports that use boost at least still compile, and ideally still
 work, however I don't have time for such testing right now.

 > Speaking of which, boost-1.56 broke `uniform_real_distribution` for
 multi-precision (see [https://svn.boost.org/trac/boost/ticket/10364]).
 Perhaps you could integrate the proposed commit
 [https://github.com/boostorg/random/commit/d4514f1e075f43e5ea7b754529740442d091b6fe]
 to fix this problem?

 Looks like that commit is in 1.60, so that will solve itself once we
 update.

-- 
Ticket URL: <https://trac.macports.org/ticket/50572#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X