Put mamba under condabin/ too

[jaimergp]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Some users have $PREFIX/condabin in PATH, and updating to mamba 2.0 breaks their workflows because it's only putting the executable under bin/, which results in errors like executable not found etc. See https://github.com/conda-incubator/setup-miniconda/actions/runs/11083642307/job/30798086717?pr=367#step:3:906.

[github-actions]

Hi! This is the friendly automated conda-forge-linting service.

I Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/mamba-feedstock/actions/runs/11103975998.}

[github-actions]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jjerphan]

Thank you for this contribution, @jaimergp.

[JohanMabille]

Thanks for your contribution! I need to check but I'm pretty sure this would break the mamba acivate / mamba deactivate features (I am swamped with fixing micromamba activate now, I'll check that right after).

[jaimergp]

We can also place a copy of the full executable there. Would that break activation?

[JohanMabille]

Back on this, these scripts should actually be generated via mamba shell init -s cmd.exe --root-prefix=$MAMBA_DEFAULT_ENV (or any shell you want to initialise) when running the miniconda installer (same for mamba forge).

[jaimergp]

when running the miniconda installer

I think this should be part of the package itself. Some setups expect mamba.bat under condabin/ because it was there for 1.x, with or without initialization. We can run the initialization routines in the package building itself, like conda does. Would that work?

[JohanMabille]

If the paths in.bat files are replaced when relocating packages, it should work and that should be the proper fix.

[jaimergp]

The only mamba subcommand I can find is mamba shell hook --shell cmd.exe %PREFIX%. I think that should work, let's give it a try.

[jaimergp]

CI now shows this for the mamba contents on Windows:

?rwxrwxrwx 0/0    1018368 2024-10-15 08:55:54 Library/bin/mamba.exe 
?rwxrwxrwx 0/0        137 2024-10-15 08:55:54 Scripts/activate.bat 
?rwxrwxrwx 0/0       1911 2024-10-15 08:55:54 condabin/_mamba_activate.bat 
?rwxrwxrwx 0/0        137 2024-10-15 08:55:54 condabin/activate.bat 
?rwxrwxrwx 0/0        874 2024-10-15 08:55:54 condabin/mamba.bat 
?rwxrwxrwx 0/0        791 2024-10-15 08:55:54 condabin/mamba_hook.bat 

[JohanMabille]

@jaimergp sorry for the long time before coming back to this! Thanks for the fix ;)