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.

Sign up for GitHub

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

Jump to bottom

Remove info_json.d & info_yaml.d logic #5498

Open
2 tasks done
kenodegard opened this issue Sep 19, 2024 · 0 comments
Open
2 tasks done

Remove info_json.d & info_yaml.d logic #5498

kenodegard opened this issue Sep 19, 2024 · 0 comments
Labels
source::anaconda created by members of Anaconda, Inc. type::feature request for a new feature or capability type::tech-debt identifies or resolves some technical debt

Comments

@kenodegard
Copy link
Contributor

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Remove unused info_json.d and info_yaml.d logic. This was originally implemented as a solution for distributing CVEs with the conda package itself.

Xref 5c3cf7e
Xref https://anaconda.slack.com/archives/C0447BASB5E/p1726698875461449

Why is this needed?

These info directories are not used today and CVEs are stored and managed separately.

What should happen?

Deprecate and remove conda.build.jsonify_info_yamls.

Additional Context

No response
@kenodegard kenodegard added source::anaconda created by members of Anaconda, Inc. type::feature request for a new feature or capability type::tech-debt identifies or resolves some technical debt labels Sep 19, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
source::anaconda created by members of Anaconda, Inc. type::feature request for a new feature or capability type::tech-debt identifies or resolves some technical debt
Projects
🧭 Planning
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kenodegard