All packages should have either a "curl" (which should be renamed to binary) package-manager-install-option or a valid object for every other package-manager-install-option, if possible. If it's not possible that should be put in the notes with a link to create an issue should it become possible to make it easy for end users to report a change in package availability.
Also, as this is being done add issues for those that need testing on the different architectures. Covers this TODO.
This may need to be split into multiple issues.
Steps to Test
curl should be renamed to binary throughout the program and index file
all packages should have a binary package or all other package managers, if neither of those can happen the notes should mention why and have a link to create an issue to request new package manager support because of a change in availability
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
mrlunchbox777@gmail.com
Feature Description
Standardize and more completely fill the index file.
Why?
There are a lot of places that the index file isn't consistent across distributions or packages which limits the effectiveness of the project.
What-should happen?
This should wait until after the initial move to golang, though it doesn't need to wait for a complete migration. It would mostly benefit from waiting until the index file is in yaml instead of json.
All packages should have either a "curl" (which should be renamed to binary) package-manager-install-option or a valid object for every other package-manager-install-option, if possible. If it's not possible that should be put in the notes with a link to create an issue should it become possible to make it easy for end users to report a change in package availability.
Also, as this is being done add issues for those that need testing on the different architectures. Covers this TODO.
This may need to be split into multiple issues.
Steps to Test
Code of Conduct