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

Subject: [boost] To modularize, or not to modularize. What is the plan?
From: Mike (mike.dev_at_[hidden])
Date: 2019-05-10 08:15:29

Before this drifts of into nothingness:
How about starting with those points from Rene's list:

> * Ban relative use of inter-library dependencies.
> * Explicit declaration of inter-library dependencies.
> * Strict normalized library layout.

Number 1 and 3 are probably already full filled by most (all?) libraries
and it is "just" a matter of cleaning up a few exceptions.

@Rene: Do you have on opinion on how exactly that normalized layout
should look like (other than what is already mandated by boost)?
More importantly: Is there any library that violates it?
Does this cover moving the "numerics" libraries into "boost/libs"?

Number 2 is useful regardless of whether boost goes full modular or
not (it e.g. can be used by depinst.py, package managers
that provides modular boost and also by cmake or other build files).

Best

Mike