You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point we have CDN enabled and working for nvidia and rapidsai channels. Thank you all for your help in setting these up! 🙏
Next we are interested in setting up repodata patching for these channels individually. Have a few questions about this:
What additional changes (if any) are needed on the backend to support repodata patching for these channels?
How would we go about making repodata patches to these channels?
2.a. Would a similar approach to conda-forge-repodata-patches work here? IOW having packages like nvidia-repodata-patches and rapidsai-repodata-patches?
2.b. Or would some other approach be needed/preferred?
I'll bring it up internally, https://github.com/AnacondaRecipes/repodata-hotfixes is the repo we're using (the old system) to make it happen, I don't think it would take a huge amount of effort to set it up for nvidia/rapidsai. That said, you know that this crosses over into partner work of Anaconda Inc and is not really just about hosting anymore. I would encourage you to coordinate with the partner manager on Nvidia's side.
At this point we have CDN enabled and working for
nvidia
andrapidsai
channels. Thank you all for your help in setting these up! 🙏Next we are interested in setting up repodata patching for these channels individually. Have a few questions about this:
2.a. Would a similar approach to
conda-forge-repodata-patches
work here? IOW having packages likenvidia-repodata-patches
andrapidsai-repodata-patches
?2.b. Or would some other approach be needed/preferred?
cc @msarahan (for awareness)
The text was updated successfully, but these errors were encountered: