Thanks for looking into this @LinasNas !

To add more context to my comment in #1672 (comment) we really have two choices,
a) fetch this information at build time.
b) fetch it during the creation of meta.yaml then permanently store the output in git.

a) would result in lighter meta.yaml but at the cost of more possibilities for build times failure if something changes in unexpected way on PyPi for instance. That's why, I think, b) would be preferable.

Here is a Python script that can fetch the description and useful URLs for each package in the Pyodide package folder.

Overall that sounds reasonable. Have a look at https://github.com/pyodide/pyodide/blob/main/pyodide-build/pyodide_build/mkpkg.py we already have some of that functionality. The idea is to,

when users run pyodide mkpkg include those fields into the generated meta.yaml
then I think you can have your own scripts to update the existing meta.yaml we don't necessarily need to include them in the repo. The ideal case would be if pyodide mkpkg --update did that, but that would likely require to merge mkpkg update improvements #1465 first.

Here is a script that would update the meta.yaml file for each package, by adding a short summary about the package, and useful URLs like links to official documentation, PyPi, or Github.

Sounds good. You might want to use ruyaml in order to preserve the order of fields in the output yaml and minimize the diff. Cf related discussion in #1465

This is an example of how the meta.yaml file in the pandas folder would look like, if the first two steps were executed

In terms of format I think it would make sense to follow conda's definition. The advantage is that it's already documented and we don't need to invent a new format. For instance see the meta.yaml for pandas. Though can add the other fields as optional if need be for instance,

about:
   documentation: <url>
   bug_tracker: <url>

We would also need to document all this in https://pyodide.org/en/stable/development/new-packages.html#the-meta-yaml-file

I fetched the package information for Step 1 from PyPi, and because several packages were not available there, their descriptions would be left empty.

Yes, that's expected, we would need to add those descriptions manually, possibly by taking them from https://github.com/conda-forge/ (preferably in a separate PR).

it's also possible to fetch a much longer description. I didn't include that part, because the meta.yaml files become quite long and less comprehensible. Here's an example of how the meta.yaml file for pandas would look like with the long description.

Yes, I agree that a long description would be too much.

Uh oh!

Make a build/index.html #977

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions