Install conda_oci_mirror to use in conda-forge-ci-setup-feedstock

[Hind-M]

Related to this conda-forge-ci-setup-feedstock PR

[Hind-M]

Hi folks,
This PR is meant to eventually add packages upload to GHCR in conda-forge (in parallel to anaconda.org). It is related to this PR in conda-forge-ci-setup-feedstock.
To make the upload happen, a Github token with the rights to upload packages in conda-forge must be used. How can it be generated (I guess only a code owner/maintainer can do that) and then added/propagated to all feedstocks?
Happy to discuss this further! Thanks.

[JohanMabille]

cc @ocefpaf

[wolfv]

I think this is clearly not ready.

First, it shoudl probably go behind a feature flag enabled by conda-forge.yml file (check how the {{ BOA }} thing works.

And then, this isn't even doing anything at this point. You could fork a feedstock somewhere in your own private repository, and then run the new conda-smithy version there to try and actually upload any packages to an OCI registry. In your fork of the feedstock, you should be able to set tokens manually. When we want to later to this via Github Actions or Azure, we probably need to set additional secrets (apparently possible via the conda-forge.yml config file (or another config file, not sure on the details). I found some code in configure_feedstock.py which reads additional secrets from the config.

[wolfv]

OK, I think I missed the bits in the conda-forge-ci-setup feedstock a bit. It would probably be better to instead add conda_oci_mirror as a package to conda-forge, and add it in the run requirements of the conda-forge-ci-setup package.