Re: [Capy review] On peer dependencies

On Tue, 23 Jun 2026 at 19:48, Vinnie Falco <[email protected]> wrote:
>
> On Tue, Jun 23, 2026 at 10:45 AM Ruben Perez <[email protected]> wrote:
>>
>> I may have explained myself incorrectly. You've got an optional header, mysql/pfr.hpp. This header includes mysql/impl/pfr.hpp for the implementation of its template functions
>
>
> What I am proposing is that if you have
>
>     #include <boost/capy/asio/asio.hpp>
>
> And we somehow inform boostdep that a directory should be ignored:
>
>     ./include/boost/capy/asio/
>
> Then the directory will simply not be scanned. If it contains impl/asio.hpp or impl/pfr.hpp, those will similarly be not scanned since they are in a not-scanned directory.
>
> I realize this is not how boostdep works today but if we want to support optional dependencies this seems the only rational way to do it without boostdep thinking that we depend on the world.

I had thought of adding the individual headers. It reflects the
current state of the art better (i.e. I don't see Asio now moving
spawn.hpp to a separate directory out of nowhere). We're likely
bikeshedding at this point though.
_______________________________________________
Boost mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.boost.org/mailman3/lists/boost.lists.boost.org/
Archived at: https://lists.boost.org/archives/list/[email protected]/message/MYAHM6MNV2SSNKO7EYBAKBT7WT5EFLU6/