conda mambabuild supports only a single recipe

[Tobias-Fischer]

As the title says, e.g. --no-test is not forwarded to conda build, and thus tests are still executed although they shouldn't.

[csachs]

I just stumbled upon a similar problem … i.e. that conda build supports multiple recipe paths to be passed, but conda mambabuild doesn't. I was just about to submit a PR to address this particular singular issue, but looking at the code, I wonder: could https://github.com/mamba-org/boa/blob/48caf3c2de11411757662d587018c62da759a432/boa/cli/mambabuild.py#L144 just be replaced e.g. by

from conda_build.cli.main_build import execute
execute(sys.argv[1:])

to just pass everything 1:1 to conda build? I did a quick test, and it seems to work fine, still apparently using mamba for solving/installing. Currently call_conda_build() does not seem to do much, but obviously it might be needed if there are more changes to be done in the future.

[wolfv]

I think this is fixed, again, with 0.4.2. sorry about that!

[csachs]

@wolfv implemented like this it will still only handle one recipe, in contrast to what the help text suggests and conda build can do

[wolfv]

Sorry

[csachs]

No problem! A quick workaround would be passing whole config.recipe not just config.recipe[0] to api.build(…) (not api.test(…) tho). But still I wonder if the 're-implementing parsing/handling logic' is even needed on the mambabuild-side, when apparently monkeypatching the solver is enough to get the desired result (fast solves with otherwise conda-build)…