On 6 Oct 2014 at 14:39, Mathias Gaunard wrote:
I'd like to ready my library for inclusion into Boost. My library is made of several modules, and I'd like to keep that into Boost.
How does Boost handles multiple submodules within a library submodule?
I'm getting a little confused as to what we mean by module, library, sub module, repository etc.
Boost is a set of libraries, which are managed by git submodules.
My own library is split in several functional modules, primarily because some of them have special dependencies and are optional.
How should this be presented for inclusion into Boost?
Boost.Thread is slowly breaking itself up into submodules. So is proposed Boost.AFIO. I would assume so will other Boost libraries over time. The technical part is easy - submit the master git super module. The hard part is management - Boost currently demands to host its own copy of every Boost library, and that gets much harder with library submodules. I guess submodule dependencies could also gain Boost copies named Boost.AFIO.local-bind-cpp-library where local-bind-cpp-library is a submodule. However, let's say local-bind-cpp-library is of terrible quality not fit for Boost. Or let's say it's a library whose control cannot be passed to Boost. Now what? It seems to me that Boost may have to not take copies of libraries. At which point we'll need a robust orphanage and preferably immediate deprecation and elimination policy. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/