Another option is to add an S-expression like (provides-srfi 1 2 3) into the .egg file of each egg that implements one or more SRFIs. This would make the information independent of the package name, and the `eggs-5-latest` Git repo already aggregates all eggs, so an indexer could clone that repo and read all the egg files to arrive at the full list of SRFIs. Can the existing tools handle a new form in those files?

This has the downside that all egg authors need to be contacted. Having a policy of `srfi-NNN` package names sounds reasonable as well.

Reply via email to