Aspera client for bioconda or conda-forge?

[bgruening]

@acaprez @npavlovikj would it be possible to contribute the aspera-cli to conda-forge or bioconda given the license allows it?

[acaprez]

Hi @bgruening. Sure, if the license allows it that's fine with us. Do you have some way to verify that?

[npavlovikj]

Maybe
https://github.com/IBM/charts/blob/master/stable/ibm-aspera-cli/LICENSES/LICENSE-IBM-Aspera-CLI
and
http://www-03.ibm.com/software/sla/sladb.nsf/displaylis/2ABD3328689EBBFE8525830C007A5F38
can help verify that?

[bgruening]

@acaprez I don't. But I guess there is no difference if this is in this repo or in bioconda.

Maybe we can copy the license @npavlovikj liked into the package and add a post-link script to echo this license? Not sure ... :(

[acaprez]

@bgruening well bioconda/conda-forge are obviously higher-profile than our little repo/channel here, so it may be under much more scrutiny. The license is quite lengthy, so I'm not sure about echoing the whole thing. Maybe a shorter "You must agree to the license" with a link would be less obtrusive to people? Of course we should include the full license in the recipe.

[npavlovikj]

Hi @bgruening ,

We updated our current "aspera-cli" recipe to the newest, 3.9.1 version, and it includes both Linux and OSX builds. Can you please take a look at the recipe, https://github.com/unlhcc/hcc-conda-recipes/tree/master/recipes/aspera-cli/3.9.1, and see if the Licence handling is ok?
If so, we can then move the recipe to bioconda or conda-forge. "aspera-cli" has a Windows version as well, and personally, I am not sure if I can make it work in case that is a requirement for the recipe to go to conda-forge...