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

Detect and filter out deprecated packages #8

Closed
kit-ty-kate opened this issue Feb 4, 2021 · 2 comments · Fixed by #9
Closed

Detect and filter out deprecated packages #8

kit-ty-kate opened this issue Feb 4, 2021 · 2 comments · Fixed by #9

Comments

@kit-ty-kate
Copy link
Contributor

We need some way of tagging packages as "deprecated" so that they don't show up when the "Only show the latest version of each packages" option is enabled.

Would a deprecated flag in the opam file work? e.g.

flags: [deprecated]
@avsm
Copy link
Member

avsm commented Feb 4, 2021

I think that's worth an upstream ocaml/opam issue, to help spec it out, as this is useful beyond health check. There have been requests for this for marking older packages that have been renamed (e.g. conduit-mirage <- mirage-conduit) or for ones the author doesn't want to support any more for their own reasons.

For these sorts of features, we could start with an x-field, but then move to deeper integration with the solver. I'd imagine an initial version could have the 0install-solver mark any packages with an x-deprecated as conflicts to the solver so they are not selected in dependencies either.

When we add fields to opam in a future revision, we could have a deprecated or alerts field to complement the current available.

@kit-ty-kate
Copy link
Contributor Author

I think I'd rather have deprecated flag than a x-deprecated field. A x-deprecated field doesn't make much sense to me as I do not see what the value would be. flags: deprecated passes the opam lint test so there is no harm in adding it.

I'll open an issue for a solver integration though, for sure.

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

Successfully merging a pull request may close this issue.

2 participants