-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package Tombstones #1900
Comments
Here is a list of some use cases for Tombstones, as well as their associated issues/pr's
|
Removed |
I believe this is more related to #823 than to tombstones |
Additionally, some are removed due to malware or publisher request such as FileZilla, which do not need to have been submitted before, but have a tombstone. Especially publisher request. The publisher request should ask you to get it from their website if they have the package available. |
Description of the new feature / enhancement
Sometimes a package is temporarily not available, or the publisher has chosen not to be included in the Windows Package Manager Community App Repository.
A new Tombstone.YAML file would be used to support this behavior.
If the file is in the package directory, it could be used to hold identifiers to help prevent future submission rather than what would likely happen if there was no manifest for the package. It may contain SHA256 values for known versions to help inform users when they try to submit a manifest that the package has been tombstoned and cannot be submitted.
If the file is in a version directory, that version would no longer be available for search, install, or upgrade, but it would still allow users who have the package (as a dependency) so they could still install software that depended on that no longer available version of a package.
If a user were to try to install a package and the specific required version of the dependency had been tombstoned, the user would be informed that the dependency is no longer available.
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered: