coderabbitai[bot]
commented
6 days ago 📝 Walkthrough
## Walkthrough The pull request introduces modifications to the `build.sh` and `meta.yaml` files for the Bindash project. In `build.sh`, environment variables such as `INCLUDES`, `LIBPATH`, and `LDFLAGS` are set to define include and library paths based on the `PREFIX` variable. A conditional block is added to adjust `CONFIG_ARGS` for macOS, disabling certain CMake features. The CMake command is updated to utilize `-S` and `-B` options for source and build directories, alongside additional flags for installation prefix and C++ compiler settings. The `make` command remains mostly unchanged, preserving its verbosity and parallel execution. In `meta.yaml`, the version number is incremented from 2 to 3, and the `run` requirements see the removal of `zlib`. Formatting updates are made to the `home`, `license`, `dev_url`, and `doc_url` fields for consistency, with the addition of a new `doc_url` pointing to the README for the specific version. The `extra` section is updated to include `osx-arm64` in the supported platforms list. ## Possibly related PRs - **#50991**: This PR adds support for `osx-arm64`, which is relevant as the main PR also includes changes to support this platform in the `meta.yaml` file. - **#51176**: This PR updates the `meta.yaml` file to include `osx-arm64` in the additional platforms, similar to the changes made in the main PR. - **#51161**: This PR adds support for `osx-arm64` in the `mashmap` package, aligning with the main PR's focus on enhancing compatibility for this architecture. - **#51505**: This PR adds `osx-arm64` as an additional platform in the `diamond` package, which is consistent with the main PR's updates to support this platform. - **#51515**: This PR also includes updates to the `diamond` package, which shares a focus on enhancing compatibility with `osx-arm64`, similar to the main PR's changes. ## Suggested labels `please review & merge`, `osx-arm64`Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add labelcommand.@bioconda/corein a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes. This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe. If not already present in the meta.yaml, make sure to specify
run_exports(see here for the rationale and comprehensive explanation). Add arun_exportssection like this:with
...being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}{{ pin_subpackage("myrecipe", max_pin="x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}while replacing
"myrecipe"with eithernameif aname|lowervariable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:@BiocondaBot please update@BiocondaBot please add labelplease review & mergelabel.@BiocondaBot please fetch artifactsYou can use this to test packages locally.
@BiocondaBot please mergecommand is now depreciated. Please just squash and merge instead. Also, the bot watches for comments from non-members that include `@bioconda/