To support this change to the conda-forge channel, especially on CentOS 7, we needed to switch to conda compilers to ensure compatibility with the provided packages - specifically, those maintained by the conda-forge community. Using the compilers provided from conda-forge
There is extensive documentation on the conda-forge site on how to add or maintain a recipe, and there are lots of helpful people in #dm-conda on Slack. Generally useful software to conda-forge when necessary. Our general approach going forward is to push third party or We have contributed, and continue to contribute, recipes for third-parties to the conda-forge community to support our software. This isn’t perfect, but we aim to improve this experience while working within the FITS standard. Most notably, we are now on cfitsio 3.47, and we have merged some code to help with that transition a bit. Significantly, most third party dependencies, including Python and non-Python (C++), come from conda-forge instead of eups now. Using conda-forge for (most) third party libraries and compilers.
If, after the change, you see some issues, please notify me and create a ticket (please use conda as a component if possible.) Switching channels to conda-forgeīy default, we have switched to conda-forge to supply our third party Python dependencies, rather than the conda distribution (“defaults”).Ĭonda-forge is a “community-led collection of recipes, build infrastructure and distributions for the conda package manager” - fundamentally using conda-build and its metadata to build package recipes, with a process to contribute those recipes, leveraging common CI infrastructure to build and rebuild recipes for multiple platforms to provide compatible binaries for all sorts of packages.
Orchestrating a change like this isn’t easy, and while I’ve tried to account for all the details, I may have missed one. The essence of this change is a new conda environment, a new compiler, and an upgrade of our third parties. After some final checks tonight and tomorrow with ci_hsc, we intend to roll this out tomorrow, April 30th. This post is to notify the Science Pipelines community of the implementation of a new conda environment from RFC-679.
0 kommentar(er)
