To further clarify, I expect the metadata file to point to have the path to
the source file. Making the specific locations on disk open for package
managers to converge on.

I, personally, think it's probably best to put the sources inside libdir,
alongside the library files and metadata files, even if that results in
duplicated files in a multi arch installation, so something like

 $(libdir)/c++/modules/$(package)/

And since in this case the package owns the directory, the layout it's
private to it.

This is also more compatible with the "frameworks" model, I think.

Daniel

On Wed, Jul 12, 2023, 19:34 Daniel Ruoso <daniel_at_[hidden]> wrote:

> On Wed, Jul 12, 2023, 19:29 Mark de Wever via SG15 <sg15_at_[hidden]>
> wrote:
>
>> If something like `usr/share/c++/module/<module-name>.json` is easier to
>> standardize, I've no objections.
>
>
> Again. This has already been the subject of extensive debate on SG15, and
> the consensus we arrived is that the metadata will be grouped by the
> library.
>
> Package managers will have to point to the module metadata file for that
> library. In the absence of that capability in the package management, the
> lowest common denominator is locating the metadata file relative to the
> linker input files.
>
> This is already embedded into the modules ecosystem tr draft.
>
> Please, let's avoid walking back on things that we spent so much effort to
> build consensus on.
>
> Daniel
>
>