Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This basically broke the JSON data for repology which made Repology to not reflect any changes in the repo
- Loading branch information
b760237
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the repology-metadata script be fixed instead to generate JSON in a reliable way?
Also, could the script include an URL of the repository a package comes from? This is required for Repology to be able to constuct a link to package sources, and is now mandatory.
Also would be nice to enable issues for https://github.com/termux/repology-metadata
b760237
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The script has some room for improvements for sure.
What should such a variable be called in the packages.json?
Do you mean a link to the root of the repo (for example https://github.com/termux/termux-packages), or a link to the package folder (for example https://github.com/termux/termux-packages/tree/master/packages/0verkill)?
It has now been enabled
b760237
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At your discretion, maybe something like
repository_url
.Well as of now, Repology usually constructs three links for a package as long as these are valid:
So it needs just enough information in order to be able to construct these links.
Repo root thus would generally be enough, but here it will only work if all repositories reside on GitHub and all packages reside under
packages/{name}
, and I'm not sure if that's true.Even if these conditions are fulfilled, it's not quite future-proof, and, given that this script is designated specifically for Repology, it may be more convenient to construct all three links right away, e.g.
Taking advantage of the opportunity, it would be nice to also have links to patches:
Thank you!