You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conda-skeleton is slow (eg. it takes 31 sec to generate the recipe for the pytest package) and sometimes generates bloated recipes by mixing up dependencies. It is tightly coupled with conda-build and that makes it difficult to make changes to it (because there is always a risk that something within conda-build itself might break).
We plan to migrate away from conda-skeleton and move towards Grayskull and eventually adopt it as the defacto conda
recipe generator. This epic will be used to keep track of all the issues related to recipe generation that may or may not be solved if Grayskull is used instead of conda-skeleton.
Please note that grayskull's CRAN implementation is not yet a replacement for skeleton implementation, and the Anaconda R builds are still relying on it. Please do not remove skeleton before the grayskull CRAN implementation is feature compatible with skeleton.
Summary
conda-skeleton is slow (eg. it takes 31 sec to generate the recipe for the
pytest
package) and sometimes generates bloated recipes by mixing up dependencies. It is tightly coupled with conda-build and that makes it difficult to make changes to it (because there is always a risk that something within conda-build itself might break).We plan to migrate away from conda-skeleton and move towards Grayskull and eventually adopt it as the defacto conda
recipe generator. This epic will be used to keep track of all the issues related to recipe generation that may or may not be solved if Grayskull is used instead of conda-skeleton.
Linked Issues & PRs
Additional resources
The text was updated successfully, but these errors were encountered: