clemgoub
Adding a bioconda recipe
Hello, I recently tried your tool, found it useful, and thought it'd be good to release it on bioconda! If you're interested, I got put in a PR to bioconda to add a recipe for this tool.
One thing that would be needed is providing release tarballs on this repo
Best
Hey! That would be amazing!
So basically I should create a release based on the GitHub repo? I might add a few quality of life improvement before (such as the ability to run on multiple sequences at a time).
Let me know if there are some specifics that needs to be in the tarball release, and I'll be happy to do it!
Cheers,
Clément
Sounds good, I will have a go at making/testing the recipe and update here
I would say, because they're easily update-able, that a first release based on current tip of main branch is already great
And will update you about the specifics of tarball release! Best
@clemgoub we're missing (at least) two things:
- A LICENCE file with the licence of your choice (I personally use MIT a lot)
- Pushing a
tagwith a first-release version number for the repo; I would have chosenv0.1.0personally, but it depends on your assessment of how much the CLI args/API will change, see here Then making a first release on your main repo using thattag, as done here
I've created a PR! https://github.com/bioconda/bioconda-recipes/pull/44954 I will update it with licence, version and release tarball when those are added by yourself
Hi there!
Sorry I didn't communicate more since our last chat. I am still interested to build a bioconda recipe for TE+Aid. FYI, @foriin recently added a .yml to support creation of a conda environment. Whether those changes affect your PR, I would like to check with you before continuing. If I understand correctly, we'll still need the LICENSE, version and release tarball right?
I'm sorry for the delays and I praise you patience!
Best,
Clément
Hello! Yes, we still a need LICENCE, version and release tarball.
It seems that it's standard to pin dependencies in the bioconda recipe meta.yaml, as I've done in my PR; however, that's a bit redundant with the TE_Aid.yaml in this repo. I'm not sure if there's a way to use the dependencies specified in TE_Aid.yaml during building of the bioconda package. Either way, shall I update the requirements of the bioconda recipe to match those in TE_Aid.yaml?
Best!
Hi @clemgoub, I'd like to use TE-Aid as a dependency of another bioconda project so it would be great to get @bricoletc 's recipe up.
-
First, you can create a LICENSE file from a template .
-
Then, you can add an initial version tag like this:
# Add tag
git tag -a v0.1.0 -m "Initial release"
#push to github
git push origin --tags
-
Finally, create a release from a tag on Github.
-
@bricoletc, I think you will need to include the biostrings dep from bioconductor and r-rcpp in your receipe.
Hello @Adamtaranto @bricoletc, sorry for the radio silence on this. I would like to get this going indeed. @bricoletc, whenever you are able to implement the biostrings dep, I can create the release with license, tag and tarball.
Cheers,
Clément
Hi @clemgoub, thanks for the quick reply. Changes to the bioconda recipe can be made independently of the release here if you want to go ahead with that.
@clemgoub, sorry, would you mind removing that tag and release and re-doing it without the extra dot after the v?
i.e. v.1.0.0 --> v1.0.0
It will confuse the pattern that bioconda uses to search for new versions otherwise.
Thanks. Bioconda recipe is good to go once the corrected release is up.
This is great, thanks for pushing to completion @Adamtaranto , all the best @clemgoub !