Thanks for this idea!

Could be that a "high-brow" approach based on Metacello metadata is an interesting alternative to a "low-brow" approach based on simply scraping the package-cache/ directory after installation.

Here is what I would really like (restating from another mail):

To make a dump of all available packages (restricting to ones with Metacello configurations is probably fine) and, for each package, to make a list of:

- The mcz files required for installation (and any other downloded resources if there are some...?)

- The sha256 hash of each mcz file (assume I can get this easily if the file is downloaded)

- The URL where the file was downloaded from / should be downloaded from in the future

Do you think this can be determined in a straightforward way from Metacello metadata?