So this Conda option enabled locally built packages with conda build to be used during installation or environment creation.

I'm working on adding this now. I'm going to add an extended example to the docs of testing a tool with locally built package from a fork of bioconda.

On Gitter @nsoranzo argued well that this option should be off by default - so I will do that as well.

John Chilton @jmchilton 15:47
I'm going to add a Galaxy flag for --use-local for use with planemo - to allow Galaxy to see packages built with conda-build. Is there any reason to have this off by default or should I just add it to every install/create command and just add a flag for disabling it?
Ping @mvdbeek @bgruening @nsoranzo ^

Nicola Soranzo @nsoranzo 15:49
I think I would prefer off by default, so that a planemo test is "reproducible" by default
Having some random local conda build always in the mix may lead to spurious issues being reported

John Chilton @jmchilton 15:52
It is a fair point - it just feels having a local conda build is so intentional - like if it is there you worked hard to get it there and it should be used. It would simplify the default state to have it off though - that is a good point.
Unless I hear from someone else it will be off by default then.

Nicola Soranzo @nsoranzo 15:54
Also, you want to submit a tool when the Conda package is online, so that would mean frequent testing with --use-local disabled anyway

--use-local conda for conda #620

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions