Re: Making Boost modular. IMPORTANT! URGENT! <insert-superlative-here>!

From: Boris Kolpackov (boris_at_[hidden])
Date: 2024-01-15 10:48:54

René Ferdinand Rivera Morell via Boost <boost_at_[hidden]> writes:

> Q: Will this require that we change the current Boost source structure?
> A: Yes. Unfortunately there is one restriction that adhering to a
> modular Boost requires. We would not allow sublibs. That is, that we
> can't support having libraries in root/libs/thing/<library> style
> locations. All libraries must be single libraries under the root/libs
> directory. Thankfully there's only a handful of such libraries. The
> root/libs/numeric/* group of libraries.

This caused us quite a bit of pain when packaging Boost for build2.
FWIW, we split numeric/* into four packages:

libboost-numeric-conversion/
libboost-numeric-interval/
libboost-numeric-odeint/
libboost-numeric-ublas/

Just to confirm, the changes that you are proposing will be backwards-
compatible from the user's perspective, right? In particular, the
public header inclusion paths will still be <boost/numeric/**.hpp>
rather than, say, <boost/numeric-conversion/*.hpp>, correct?