Open hjoliver opened 2 years ago
Ideas for 2:
Mentioned in #130, https://github.com/cylc/cylc-admin/issues/130#issuecomment-912958651
Conda Forge package versions labelled as broken are ignored by conda install
.
Marking package versions as broken involves forking conda-forge/admin-requests and making a PR to add a broken/<blah>.txt
file that lists the broken package versions.
For the old cylc meta package, we'd have to list all of these: https://anaconda.org/conda-forge/cylc/files
We could try this, but I'm not sure it would fly with the Conda Forge reviewers, because the packages are not technically broken.
Alternatively, or as well, we could post a new final version of the meta package that updates the description in the recipe and (if we can get away with it) replaces all the project files with an informative README file.
Let's make a decision in the next meeting, if not before.
There are two cylc conda packages that we stopped publishing at older versions.
the "cylc" meta-package
We abandoned this after 8.0b1, so if a user (quite reasonably) types
conda install cylc
they will get ancient development releases of our components.cylc-ui
We stopped publishing this as a separate conda package after 8.0rc1. In the 23 May Cylc meeting, no one present could remember if this was a deliberate decision or not. We don't need it as a separate package (it is bundled with
cylc-uiserver
), but older versions were published so we should do something to indicate they should not be user.