Adding a bioconda recipe

[bricoletc]

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

[clemgoub]

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

[bricoletc]

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

[bricoletc]

@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 tag with a first-release version number for the repo; I would have chosen v0.1.0 personally,
  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 that tag, as done here

[bricoletc]

I've created a PR! bioconda/bioconda-recipes#44954
I will update it with licence, version and release tarball when those are added by yourself

[clemgoub]

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

[bricoletc]

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!