Use `return` in activate/deactivate scripts

jakirkham commented 5 years ago

Partially addresses https://github.com/conda-forge/nvcc-feedstock/issues/22

With scripts that are being sourced, it is recommended to use return instead of exit. This ensure the sourced script errors out without accidently exiting from a user session as well.

cc @pearu

Checklist

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

conda-forge-linter commented 5 years ago

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) and found it was in an excellent condition.

jakirkham commented 5 years ago

FWIW also tried this myself locally and it had the right error handling behavior.

conda-forge / nvcc-feedstock

Use `return` in activate/deactivate scripts #24