I'm all in favour of a standardised, minimal way of expressing SRFI
support, or maybe even general features (eg 'this implementation has
native threads') for each implementation. It's worth noting that this
won't be possible for unmaintained implementations, but fortunately their
respective feature sets aren't likely to change any time soon. :-)

> > There's also unnecessary bandwidth being wasted repeatedly downloading
> > tar files, and time spent uncompressing and searching through them for
> > what amounts to a relatively tiny bit of data.
>
> These are non-issues. GitHub and GitLab have tons of bandwidth. Gambit
> is one of the biggest Schemes and running listings/gambit-head.sh takes
> only 4 seconds, including the time GitHub takes to generate us a
> tailor-made tar archive of Gambit's git master.
>

FWIW I'm experimenting with scripts that directly query the GitHub API.
See `external.rkt' in the repo. It might or might not be a cleaner
solution. We'll see!

--
~erkin