Re: [Capy review] On peer dependencies

El 23/06/2026 a las 19:47, Vinnie Falco via Boost escribió:
> 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.

boostdep can be blocked this way:

https://github.com/boostorg/multi_index/blob/develop/include/boost/multi_index/detail/mpl_to_mp11_list.hpp

The trick seems quite reasonable to me, as it does what it says and the 
intent is clear.

Joaquín M López Muñoz

_______________________________________________
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/TUWOH2XCWISSOJK4DIAO4DFWR4ZYQPIT/