Subject: Re: [boost] [modularization] What do we do with "glue" headers?
From: Daniel James (daniel_at_[hidden])
Date: 2013-10-19 12:59:23
On 19 October 2013 17:40, Andrey Semashev <andrey.semashev_at_[hidden]> wrote:
> On Saturday 19 October 2013 18:23:54 Mathias Gaunard wrote:
>> On 19/10/13 12:22, John Maddock wrote:
>> > A good example would be the serialization lib: a simple dependency
>> > tracker would show this up as a dependency to a large part of Boost, but
>> > in fact that's not true: in the vast majority of those cases there is no
>> > such dependency unless you actually want to use both libraries together
>> > and do so by including the "glue" header.
>> > So where does the glue header belong?
>> In a submodule of the library that depends on both the rest of the
>> library and serialization.
>> I don't see any need for optional dependencies here.
> IMHO, having glue headers in separate repositories is very inconvenient.
We could set it up so that a single repo could contain multiple
submodules (i.e. a module for dependency checking is not the same
thing as a git submodule).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk