coderabbitai[bot]
commented
6 days ago 📝 Walkthrough
## Walkthrough This pull request introduces several changes across three main files related to the Masurca software installation and build process. In the `install.sh` script, the `autoreconf -if` command is added to regenerate configuration files, and the `cp` command is modified to `cp -arf` for improved file copying behavior. The `build.sh` script sees updates to environment variable exports, including the use of double quotes for consistency and changes in optimization flags from `-O2` to `-O3`. The handling of library paths during linking is also adjusted. The `meta.yaml` file is updated with a new version number, the addition of a patch file, and several new build dependencies, including `automake`, `autoconf`, `libtool`, and `pkg-config`. Additionally, the formatting of metadata fields is improved, and new fields for development and documentation URLs are added. Overall, these changes enhance the installation and build processes for the Masurca package. ## Possibly related PRs - **#51221**: The `build.sh` script in this PR includes the addition of the `autoreconf -if` command, similar to the changes made in the main PR's `install.sh` script, which also modifies the build configuration process. - **#51641**: The `build.sh` script updates the `CXXFLAGS` to include optimization flags and changes the C++ standard, which aligns with the main PR's focus on enhancing build configurations through similar modifications. ## Suggested labels `please review & merge`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/