You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CPAN provides a snapshot file (02packages.details.txt.gz) downloadable from a known location, and also keeps the non-gz version of that file in a git repository so one can spelunk history.
Both are definitely valuable - as is a web service for querying said index (ala https://cpanmeta.grinnz.com/packages) but git as the primary storage for the index metadata is IMO obviously correct in 2021.
This is not entirely true for -data- rather than -metadata- since it's essential to have a (human mediated) means to completely delete a tarball if it accidentally contains proprietary information or API keys or something like that but for the pure metadata, sure, stick it in git.
(to anybody who might say "well, it's out there anyway at that point" my answer would be that, yes, I know, but refusing to delete such an upload is a good way to have corporate lawyers ban uploading anything ever, and whether that's sensible or not, I don't want to punish somebody for trying to contribute to open source and I don't want to accidentally cause entire companies to ban trying to do so any more than they already do)
Any other formats you might want therefrom should be produced using the moral equivalent of cron jobs.
We have two possible courses of action here regarding the package index:
The text was updated successfully, but these errors were encountered: