Determining the correct, most up-to-date source/document for scraping CHICKEN SRFI metadata from

[diamond-lizard]

This project's srfi table scraper currently gets its information regarding which SRFIs the latest version of Chicken supports from this document:

https://github.com/diamond-lizard/chicken-srfi-support/blob/main/srfi-table.org

That is my own personal org-mode document I originally used to create this Chicken wiki page:

https://wiki.call-cc.org/srfi-support

The problem is that no one else uses my org document. Other Chicken developers and maintainers just make changes directly to the Chicken wiki.

What I do when that happens (and when I notice and have time, which is usually when releasing my own new Chicken SRFI eggs) is I'll manually update my org document to be in sync with the Chicken wiki page, make my own changes to the org document, export it as html, put the <table> portion of the html on to the Chicken wiki (which mercifully can understand the HTML table format that org spits out).

Needless to say, this manual process can easily result in my org document getting out of sync with what SRFIs Chicken actually supports. But, regardless, my personal org-mode file should probably not be scraped because it's not authoritative or used by anyone else.

Worse, the above Chicken wiki page is not the only page which documents which SRFIs Chicken supports.

There's also this page:

http://wiki.call-cc.org/supported-standards

Which was one of the sources I originally scraped to get the information for my own org document and the table generated from it on the srfi-support page linked above.

Also, there's this page:

http://wiki.call-cc.org/SRFI-conformance

which is pretty out of date -- the last change was in 2019.

Finally, when new eggs are published in the official Chicken repo (its "coop") they're put on this page:

http://eggs.call-cc.org/5/

But that page is not SRFI-specific.

This last page may be the most authoritative one out of them all, but there's no way to know if an egg on there is actually a SRFI egg unless its name begins with "srfi" (which is true for most eggs that provide SRFI support, but not all). It also does not list any SRFI support that's built in to Chicken. For that information you'll have to look at the http://wiki.call-cc.org/supported-standards page.

It may be a good idea to bring this issue up on the chicken-users mailing list, to which you can subscribe here:

https://lists.nongnu.org/mailman/listinfo/chicken-users

It's also possible to discuss it on the #chicken channel on freenode, but not everyone is present or awake there at the same time, so the mailing list would probably have a greater chance of getting everyone in to the conversation.

[lassik]

Thanks for the excellent survey and your continued work on Chicken!

I agree that it's best to ask the Chicken maintainers what to do. I'm subscribed to -users as well. Can you ask them to look at this thread?

[diamond-lizard]

Can you ask them to look at this thread?

Done.

[jpellegrini]

What about asking Henrietta directly for the extra eggs?

$ curl http://code.call-cc.org/cgi-bin/henrietta.cgi?list=a\&release=5|grep srfi
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0srfi-101
srfi-193
srfi-95
srfi-4-utils
srfi-127
srfi-128
srfi-78
srfi-117
srfi-38
srfi-102
srfi-99
srfi-63
srfi-34
srfi-123
srfi-40
srfi-45
srfi-41
srfi-9-ext
srfi-71
srfi-133
100  7818    0  7818    0     0  16275      0 --:--:-- --:--:-- --:--:-- 16287
srfi-25
srfi-4-comprehensions
srfi-29
srfi-42
srfi-116
srfi-113
srfi-modules
srfi-19
srfi-60
srfi-121
srfi-37
srfi-7
srfi-27
srfi-64

Needs to be adapted, of course...

[jpellegrini]

This is Henrietta, listing her own code:

http://code.call-cc.org/cgi-bin/henrietta.cgi?name=henrietta&release=5

[wasamasa]

I suspect this again can be closed because the scraper in https://github.com/schemedoc/srfi-metadata/blob/master/external.rkt consults the supported standards wiki page and the egg locations list. While henrietta can be consulted, it merely lists the eggs sitting on that mirror which themselves are fetched using henrietta-cache from the egg locations list, so that's no improvement.