Support for macOS arm64 on BioConda

[nrminor]

Hello,

I'm working on fully supporting M-series MacOS machines in one of my Nextflow pipelines, and fq is one of its last conda dependencies that isn't available for the platform on BioConda. The project compiles successfully on the ARM Mac I'm currently working on, so I'm curious if there's anything I can do to help get macOS arm64 support up and running on BioConda. It looks like you already include it in your CD release matrix, though a corresponding binary doesn't show up in your releases. Perhaps there's an issue between that workflow and the conda feedstock that I can help address?

Thanks!

[nrminor]

Just a quick follow-up - it looks like supporting ARM Macs may be as simple as adding an additional platforms line to your meta.yaml:

extra:
  additional-platforms:
    - linux-aarch64
    - osx-arm64 # added line

[zaeleus]

Thanks for letting us know that the aarch64 macOS build was missing from Bioconda. I submitted the recipe update, and it can be tracked at bioconda/bioconda-recipes#61243.

[nrminor]

Thanks for doing that!

[nrminor]

@zaeleus it may be that the only way you can get around the new name collision policy is to publish fq under a name that disambiguates it, e.g., fq-bio. Presumably the executable could still keep the same name. I think conda works like crates.io in that sense.

[zaeleus]

After working with the Bioconda team, bioconda::fq will retain its package name, as it predates the one on conda-forge. conda-forge::fq is in the process of renaming (conda-forge/fq-feedstock#9) to fix the name collision. I'll rerun the bioconda tests after this happens.

The cause of this conflict is likely from conda-forge not failing on name collisions (conda-forge/staged-recipes#29880).

[nrminor]

Sounds good, glad it worked out that way! I'll keep an eye out for the aarch64 macOS build whenever the collision resolves.