From db7bcbe8cf6d02c49f2191fea1bc0232859c2e6b Mon Sep 17 00:00:00 2001 From: Wolf Vollprecht Date: Sat, 15 Feb 2025 19:35:05 +0100 Subject: [PATCH] Update news/2025-02-13-conda-forge-v1-recipe-support.md Co-authored-by: jaimergp --- news/2025-02-13-conda-forge-v1-recipe-support.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/news/2025-02-13-conda-forge-v1-recipe-support.md b/news/2025-02-13-conda-forge-v1-recipe-support.md index c900c82c12..c373576d95 100644 --- a/news/2025-02-13-conda-forge-v1-recipe-support.md +++ b/news/2025-02-13-conda-forge-v1-recipe-support.md @@ -55,7 +55,12 @@ If you are adding a new recipe on staged-recipes, then it's easy: just submit a In case you already maintain a feedstock, then the conversion can be semi-automated with a tool created by [Hadrien Mary](https://github.com/hadim) called [`feedrattler`](https://github.com/hadim/feedrattler). The tool will take care of the basic conversions steps and uses [`conda-recipe-manager`](https://github.com/conda-incubator/conda-recipe-manager) by Anaconda / [Schuyler Martin](https://github.com/schuylermartin45) under the hood to parse the recipe and convert it to the new format. ```shell +# One liner with Pixi pixi exec feedrattler my-awesome-package-feedstock gh_user +# With conda or mamba (as $CONDA) +$CONDA create -n feedrattler feedrattler +$CONDA activate feedrattler +feedrattler my-awesome-package-feedstock gh_user ``` To do the conversion by hand, you need to do the following things: