Skip to content
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

"Deprecate a package" should include instructions for package which are not being superseded #948

Open
chtof opened this issue Feb 10, 2024 · 2 comments

Comments

@chtof
Copy link

chtof commented Feb 10, 2024

What You Are Seeing?

https://docs.chocolatey.org/en-us/community-repository/maintainers/deprecate-a-chocolatey-package:
There are only instructions to deprecate a package which is being superseded. It does not work when a package are not being superseded as it's not possible to provide a dependency on a new package.

What is Expected?

Instructions to take into account packages which are not being superseded.

How Did You Get This To Happen? (Steps to Reproduce)

A package can't be validated if there is no dependency and no <files>...<files/> embedded.

@TheCakeIsNaOH
Copy link
Member

My understanding is that in these sorts of situations that all versions of the package should be unlisted, with no need to push a final version.

@pauby
Copy link
Member

pauby commented Feb 10, 2024

I think this is a misunderstanding of what a deprecated package is.

A package is deprecated in favour of another package.

A package whose software is no longer available just needs to be unlisted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants