Mervin Fansler

[The DESCRIPTION file](https://github.com/cran/survtmle/blob/295de8b4be182bc6696afd2ef06f0f738d3a5eae/DESCRIPTION#L28) reports no compilation. There are some sections in the Knowledge Base that pertain to targeting additional platforms, e.g., [**osx-arm64**](https://conda-forge.org/docs/maintainer/knowledge_base.html#apple-silicon-builds), [**linux-aarch64**](https://conda-forge.org/docs/maintainer/knowledge_base.html#using-arch-rebuild-txt). Admittedly, they don't describe in detail the...

@conda-forge/staged-recipes looks good to me

Why so many packages together? Does `r-filearray` require all these additional packages to be added?

@dipterix Apologies if there was a miscommunication. My previous comment was to submit *interdependent* recipes together. For example, if you have a package, **A**, you wish to submit, and it...

@conda-forge/staged-recipes looks ready to merge

R *libraries* also deliver into predictable directories and similarly diverge from the package names (though the `r-` and `bioconductor-` patterns for package naming are nearly ubiquitous).

I'd vote to build both. Bioconductor is too core to bioinformatics users to have a gap in versions. The Conda Forge R 4.2 migration is mostly done, BTW.

The problem here is likely not correctly prioritizing `conda-forge` channel (dynamic library errors usually arise from [improper channel mixing](https://conda-forge.org/docs/user/tipsandtricks.html#using-multiple-channels)). Any *ad hoc* use of Bioconda channel should take the form:...

I also like 2 (`bioconda`), but that's also my field. 😏 Not sure if it's relevant here, but I've gotten in the habit - and regard it best practice for...

This should probably be [an Issue on the `cdt-builds` repository](https://github.com/conda-forge/cdt-builds/issues) instead.