Subject: Re: [boost] GitHub testing issues
From: Peter Dimov (lists_at_[hidden])
Date: 2018-12-19 18:57:57
Rene Rivera wrote:
> This had NOTHING to do with Boost Build. It was a Boost change.
Correct. It is a matter of physical organization, moving work from the
superproject to submodules.
Having and developing functionality in the superproject is incredibly
inconvenient; doing development in a submodule is much more manageable.
Unfortunately, the flip side is that the superproject is no longer
self-sufficient, you have to checkout a few necessary submodules along with
it.
This was already true; you needed at minimum tools/build. And, since at some
point tools/build was made dependent on libs/config, you then had to
checkout libs/config too, for things to function.
The change added two other necessary submodules to that list.
This only affects people who do partial Boost checkouts in their Travis and
Appveyor .yml files. If you test against a release, or a full recursive
clone, nothing changes.