Adapt distribution of etc/profile.d/mamba.sh

[jjerphan]

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.

Fix #282 with a patch of mamba-org/mamba#3723.

[jjerphan]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12596639646. Examine the logs at this URL for more detail.}

[conda-forge-admin]

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.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12634644016. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12596662575. Examine the logs at this URL for more detail.}

[maresb]

Hey @jjerphan, sorry that #282 was confusing. (What I put under "Installed packages" in that report were the commands that I used to achieve a broken environment with a mambaorg/micromamba container.)

By the way, I downloaded the 2.0.5 mamba packages from conda-forge for Windows and Linux. The Linux version doesn't seem to include any activation scripts (presumably they are currently provided transitively by libmamba). In contrast, the Windows version of mamba does include activation scripts in Scripts/ and condabin/ 🤔.

Another thought: would it be possible for someone on Linux to end up with build 2 of libmamba without the mamba.sh included in libmamba but with build 1 of mamba that also excludes mamba.sh? Answer: All good, this potential problem seems impossible because the pin on libmamba seems to include the build number.

[maresb]

Should be .bat on Windows. Also suggesting to use the identical path from the mamba section below.

Suggested change

	- if exist %LIBRARY_PREFIX%\etc\profile.d\mamba.sh (exit 1) # [win]
	- if exist %PREFIX%\condabin\mamba.bat (exit 1) # [win]

[jjerphan]

This tests that the file is also not present on Windows (this can be misread at first).

I think we could move this check at the top with the one for [unix] with a comment giving the motivation and to remove the confusion.

[maresb]

Note that I'm only claiming is that the mamba.sh/mamba.bat activation script should not be included with libmamba.

Probably your claim is correct, but it caught my eye. (It's been a long time since I've looked at the activation scripts for micromamba, and indeed the latest micromamba package doesn't seem to include any activation scripts.)

[jjerphan]

For reference, this change was added based on this test in micromamba-feedstock independently from your remark.