frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: 114 Chapter 1. User guide conda, Release 23.7

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: 114 Chapter 1. User guide conda Documentation

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: 1.7. Troubleshooting 115 conda Documentation,

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%

frequently an "output" in a recipe that builds some variant of another package. Mutex metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at batch scripts, you must prefix your command with CALL. If you do not do this, your batch script that calls conda will exit immediately after the conda usage. In other words, if you write this in a .bat file: in the system settings. For example, a new conda prompt batch file that first strips PATH, then calls the correct activation procedure could look like: set PATH=”%SystemRoot%\system32;%SystemRoot%;%