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

On Tue, May 7, 2019 at 10:59 AM Peter Dimov via Boost wrote:

Robert Ramey wrote:

...

Get me boost library X and place in directory location Y.

This is at present roughly achievable with the following sequence of commands:

git clone --depth 1 https://github.com/boostorg/boost.git cd boost git submodule update --init tools/boostdep libs/$X python tools/boostdep/depinst/depinst.py -X test $X ./bootstrap.sh ./b2 --prefix=$Y --with-$X install

But that's an entirely different use case. This is

Boost Github -> user

as opposed to

Boost Github -> Boost release -> package manager (apt, conan, vcpkg) -> user

More accurately, GitHub -> release -> package manager (apt, conan, vcpkg, ...) The intention of this exercise is to eliminate the monolithic build and allow each repository to release whenever it wants, following SemVer rules for major,minor,patch and leverage versioned dependencies, correct? If not, why would we do it? We would also want to train a project like dependabot how to spot and help us keep our dependencies up to date. - Jim