-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add seq2squiggle recipe #53053
Add seq2squiggle recipe #53053
Conversation
Head branch was pushed to by a user without write access
Hi @bioconda/core @martin-g Is there a way to include a dependency from a channel outside of conda-forge and bioconda? Specifically, I'm trying to add POD5 (v0.3.23) as a dependency, but it's currently only available on the nanoporetech channel. Without this, my package cannot be installed due to the missing dependency. Would appreciate any guidance on how to handle this scenario or suggestions for potential workarounds. Thanks in advance! |
Reposting for @denisbeslic to enable pings (courtesy of the BiocondaBot):
Is there a way to include a dependency from a channel outside of conda-forge and bioconda? Specifically, I'm trying to add POD5 (v0.3.23) as a dependency, but it's currently only available on the nanoporetech channel. Without this, my package cannot be installed due to the missing dependency. Would appreciate any guidance on how to handle this scenario or suggestions for potential workarounds. Thanks in advance! |
Only conda-forge and bioconda channels are supported. If you can add to bioconda (in another PR), that would work, assuming that pod5 doesn't have dependencies in unsupported channels (and the license allows it). |
Thanks! I was able to find an older version of pod5 on bioconda! |
@BiocondaBot please add label |
This PR adds seq2squiggle.
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add label
command.@bioconda/core
in 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 a
run_exports
section 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 eithername
if aname|lower
variable 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 label
please review & merge
label.@BiocondaBot please fetch artifacts
You can use this to test packages locally.
Note that the
@BiocondaBot please merge
command is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.