Currently we are slow to update this feedstock - partially due to limited resources, but also since we wait to apply changes with each cyclus/cyclus release. One method to apply new changes to the feedstock is using patches, but then the version number associated with the package is not aligned with the version tag in the git repository. Alternatively, conda-forge provides the ability to publish different versions of a package simply by maintaining different branches. They present a good use case for this: maintaining a dev or rc package.
I think it could be valuable to maintain a dev package for cyclus to help stay on top of this feedstock, analogous to the approach that we take with our :latest container images. It would help with maintenance efforts, make CI for macOS cyclus simpler for downstream projects, and allow users to easily install cyclus with the latest features.
@gonuke do you have any thoughts/concerns about going down this road?
Currently we are slow to update this feedstock - partially due to limited resources, but also since we wait to apply changes with each
cyclus/cyclusrelease. One method to apply new changes to the feedstock is using patches, but then the version number associated with the package is not aligned with the version tag in the git repository. Alternatively, conda-forge provides the ability to publish different versions of a package simply by maintaining different branches. They present a good use case for this: maintaining adevorrcpackage.I think it could be valuable to maintain a
devpackage for cyclus to help stay on top of this feedstock, analogous to the approach that we take with our:latestcontainer images. It would help with maintenance efforts, make CI for macOS cyclus simpler for downstream projects, and allow users to easily install cyclus with the latest features.@gonuke do you have any thoughts/concerns about going down this road?