On Mon, Apr 26, 2021 at 12:04 AM Lassi Kortela <xxxxxx@lassi.io> wrote:
>
> >     It is not so much a “package manager” that is needed but rather the
> >     specification of a “package structure” that all of the libraries
> >     would need to follow (e.g. a git repository would need such and such
> >     a file and subdirectory in such and such a place of the main
> >     directory).  Then each Scheme implementation can extend their
> >     current package manager to install these libraries.
>
> +1

This is exactly what snow-fort defines:

  http://snow-fort.org/doc/spec/

It currently has two client implementations to choose from and one
(super basic) host (snow-fort), but was specifically designed to make
it easy to decentralize, and e.g. allow each author to host their own
packages on their own github pages.

It may not have everything you want but is a simple and extensible
format, and the site has been in active use since 2015.

The nicest aspect is that apart from the meta-data all you need to
specify is the relative path to the file where each library is defined.
This means developers can keep whatever layout and file naming
conventions they want.  Otherwise they need tools to convert their
source into your prescribed package structure as a separate
publishing step, and so the published version becomes second
class.  This creates extra work and discourages community patches.

--
Alex