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

Write and vote on CEP to specify the next-gen recipe format #4755

Closed
Tracked by #4697
jezdez opened this issue Jan 26, 2023 · 2 comments
Closed
Tracked by #4697

Write and vote on CEP to specify the next-gen recipe format #4755

jezdez opened this issue Jan 26, 2023 · 2 comments
Assignees
@wolfv
Labels
severity::3 major; broken functionality with a workaround source::anaconda created by members of Anaconda, Inc. source::community catch-all for issues filed by community members source::partner created by or for an Anaconda, Inc. partner company type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package

Comments

@jezdez
Copy link
Member

jezdez commented Jan 26, 2023 •
edited by wolfv
Loading

This is currently called the “boa format” and has been discussed between @wolfv, @chenghlee, @jaimergp and me before in context of conda-build. There is also lots of prior discussion to consider (e.g. in the ticket mentioned above), to make sure the work on boa is appropriately ported.

It would be excellent to get started with the specification process (via a CEP) to formalize the format as a foundation for implementing it in conda-build directly.
@jezdez jezdez added source::anaconda created by members of Anaconda, Inc. type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package severity::3 major; broken functionality with a workaround source::partner created by or for an Anaconda, Inc. partner company source::community catch-all for issues filed by community members labels Jan 26, 2023
@jezdez jezdez mentioned this issue Jan 26, 2023
Open
2 tasks
@jezdez
Copy link
Member Author

jezdez commented Oct 23, 2023

conda/ceps#54 is that CEP and Wolf has been working on it

@wolfv
Copy link
Contributor

wolfv commented Aug 8, 2024

I guess this can be closed! 🚀 Currently writing the blog post about the ongoing conda-forge integration of the new recipe format :)

@wolfv wolfv closed this as completed Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wolfv wolfv

Labels
severity::3 major; broken functionality with a workaround source::anaconda created by members of Anaconda, Inc. source::community catch-all for issues filed by community members source::partner created by or for an Anaconda, Inc. partner company type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package
Projects
🧭 Planning
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jezdez @wolfv