Build conda package

[uwefladrich]

Since the rest of the ScriptEngine world is already on conda-forge (scriptengine and scriptengine-tasks-hpc) and since scriptengine-tasks-ecearth needs a conda environment anyway to install dependencies, we should provide a conda package on conda-forge.

[uwefladrich]

Pinging @zklaus, because we may need the expertise:

The easiest (naive?) way would be to follow the same approach as for the other SE packages: Build and publish a PyPI package in the CI actions and then let conda-forge feedstock repository pull and build a conda package. Maybe that makes sense, but it also feels a bit like beginning at the wrong end. After all, the PyPI package doesn't easily install outside a conda package anyway, so why would we need it in the first place?

[zklaus]

The way I see it, the Pypi release is the actual release, i.e. the product. It should always be installable easily, but with the caveat that it does not take care of the dependencies, particularly in the case of the source distribution. As such, I think doing the (source) release on Pypi is unquestionably the first step.

[uwefladrich]

Okay, thanks! So that means that, since we already have the ci pipeline for publishing to PyPI, we can proceed along the lines of scriptengine and scriptengine-tasks-hpc. I will try to set up the PR to conda-forge/staged-recipes. I may come back for help 😁

[uwefladrich]

See conda-forge/staged-recipes#21022

[valentinaschueller]

This is done!
Do you also want to update the documentation accordingly as part of this issue or should we create a new issue for that?

[uwefladrich]

I have added #96. Should not be too complicated, but I am not sure how quick I manage to do it. So whoever of us is first makes a suggestion, would that be okay?