"Arthur A. Gleckler" <xxxxxx@speechcode.com> writes:

[...]
> [...] Even adding metadata for all of R7RS and Snow would not make
> such an approach impractical. This has the benefit of eliminating the
> latency of fetching results from a server. It also makes clients less
> dependent on the network to get the data, and it eliminates our need
> to run a server at all beyond serving static files. As far as I can
> tell, that this would eliminate our need to run a SQL server, too.

I have been following your discussion and have seen you mention Snow
here and there. It happens that I maintain a package manager called Akku
(or Akku.scm for easier web searches) where I just now added all
snow-fort.org packages:

  https://akkuscm.org/
  https://akkuscm.org/packages/

The archive software generates a file with metadata from all packages:

  https://archive.akkuscm.org/archive/metadata.scm.xz

Perhaps you will find the information useful. It contains a list of all
packages, which libraries they import and which identifiers they export.
The chez-srfi package provides most SRFIs, so you can perhaps compare
the data with your own parsers.

There are no procedure signatures since this information is not readily
available without an R6RS/R7RS frontend, so it's a bit too much effort
for a package manager. The file format is very close to how Akku works
internally, so my apologies if the format has oddities.

Regards,

--
Göran Weinholt
https://weinholt.se/