Re: [boost] To modularize, or not to modularize. What is the plan?

On May 10, 2019, at 11:11, Mateusz Loskot via Boost wrote:

On Fri, 10 May 2019 at 09:30, Steve Robbins via Boost wrote:

$ boost install github.com/boostorg/hello

import ( github.com/boostorg/hello )

On my system, I have boost installed by macports, and it has its own system to manage the optional components. One of them is MPI, and the resulting libraries depend on MPI. I wander how this affects the optimists assumptions? The second observation is that the boost dylibs have no version information whatsoever on them!!! /opt/local/lib/libboost_log-mt.dylib: /opt/local/lib/libboost_log-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_atomic-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_chrono-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_thread-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_date_time-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_filesystem-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_system-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libboost_regex-mt.dylib (compatibility version 0.0.0, current version 0.0.0) /opt/local/lib/libicudata.58.dylib (compatibility version 58.0.0, current version 58.2.0) /opt/local/lib/libicui18n.58.dylib (compatibility version 58.0.0, current version 58.2.0) /opt/local/lib/libicuuc.58.dylib (compatibility version 58.0.0, current version 58.2.0) /opt/local/lib/openmpi-devel-mp/libmpi_cxx.40.dylib (compatibility version 41.0.0, current version 41.0.0) /opt/local/lib/openmpi-devel-mp/libmpi.40.dylib (compatibility version 41.0.0, current version 41.1.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.4) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.250.1)