ChiantiPy icon indicating copy to clipboard operation
ChiantiPy copied to clipboard

conda-forge package

Open epassaro opened this issue 4 years ago • 4 comments

Recently, I uploaded ChiantiPy to the conda-forge channel: https://anaconda.org/conda-forge/chiantipy.

I think I should have to ask you before doing it, but it's already done. Currently versions available are 0.11.0 (latest) and 0.8.4 (required by carsus).

epassaro avatar Jun 25 '21 20:06 epassaro

I am not sure how this will play out if ChiantiPy is updated Ken

kdere avatar Jun 26 '21 13:06 kdere

Conda forge will automatically pick up each new release that gets uploaded to PyPI and open a PR against the chiantipy recipe repo. Releasing the new version on conda forge then is just a matter of merging that PR (provided the tests pass). E.g. the aiapy recipe repo: https://github.com/conda-forge/aiapy-feedstock

wtbarnes avatar Jun 26 '21 17:06 wtbarnes

Yes, this is an example of how the bot works: https://github.com/conda-forge/chiantipy-feedstock/pull/2. Human intervention is just required when you need to make changes to the package recipe (for example: adding new dependencies).

People with write access to the feedstock repository are listed at the bottom of the recipe. Currently, I'm the only maintainer but that's not ideal. I can add more maintainers to the recipe.

I created the package because we want to release carsus on conda-forge soon, and all the dependencies must exist on that channel.

epassaro avatar Jun 26 '21 19:06 epassaro

Conda forge will automatically pick up each new release that gets uploaded to PyPI and open a PR against the chiantipy recipe repo. Releasing the new version on conda forge then is just a matter of merging that PR (provided the tests pass). E.g. the aiapy recipe repo: https://github.com/conda-forge/aiapy-feedstock

I enabled the automerge bot, so there's no need to do anything except for breaking changes (adding new dependencies, for example).

epassaro avatar Jul 14 '21 20:07 epassaro