@@ -54,8 +54,8 @@ environment):
5454``` bash
5555conda config --add channels conda-forge
5656conda config --set channel_priority strict
57- conda create -y -n mpas_dev --file dev-spec.txt
58- conda activate mpas_dev
57+ conda create -y -n mpas_analysis_dev --file dev-spec.txt
58+ conda activate mpas_analysis_dev
5959python -m pip install --no-deps --no-build-isolation -e .
6060```
6161
@@ -64,16 +64,16 @@ for MPAS-Tools or geometric\_features), you should first comment out the other
6464package in ` dev-spec.txt ` . Then, you can install both packages in the same
6565development environment, e.g.:
6666``` bash
67- conda create -y -n mpas_dev --file tools/MPAS-Tools/conda_package/dev-spec.txt \
67+ conda create -y -n mpas_analysis_dev --file tools/MPAS-Tools/conda_package/dev-spec.txt \
6868 --file analysis/MPAS-Analysis/dev-spec.txt
69- conda activate mpas_dev
69+ conda activate mpas_analysis_dev
7070cd tools/MPAS-Tools/conda_package
7171python -m pip install --no-deps --no-build-isolation -e .
7272cd ../../../analysis/MPAS-Analysis
7373python -m pip install --no-deps --no-build-isolation -e .
7474```
7575Obviously, the paths to the repos may be different in your local clones. With
76- the ` mpas_dev ` environment as defined above, you can make changes to both
76+ the ` mpas_analysis_dev ` environment as defined above, you can make changes to both
7777` mpas_tools ` and ` mpas-analysis ` packages in their respective branches, and
7878these changes will be reflected when refer to the packages or call their
7979respective entry points (command-line tools).
0 commit comments