This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
other:uvcdat:cdat_conda:cdat_8_0_py2 [2019/03/04 09:33] jypeter [Installing CDAT nightly] Added update question |
other:uvcdat:cdat_conda:cdat_8_0_py2 [2019/03/04 10:47] jypeter [Getting ready for a moving default CDAT] Added warning |
||
---|---|---|---|
Line 292: | Line 292: | ||
</code> | </code> | ||
+ | |||
+ | ==== cdat nightly case ==== | ||
+ | |||
+ | ''conda create -n cdatm-nightly_py2 %%--%%clone cdat-nightly_py2'' | ||
===== Getting ready for a moving default CDAT ===== | ===== Getting ready for a moving default CDAT ===== | ||
+ | |||
+ | <note warning>This step should probably be listed at the **end**, especially in a multi-user environment! If there is already a ''cdatm'' link, make sure that the new version is stable and working correctly before updating the ''cdatm'' link</note> | ||
We create a **//cdatm// symbolic link** in the ''envs'' directory, that has a //stable name// but can be moved to point to the latest default CDAT. In that case, most users can just activate this //cdatm// version and always get the latest stable version | We create a **//cdatm// symbolic link** in the ''envs'' directory, that has a //stable name// but can be moved to point to the latest default CDAT. In that case, most users can just activate this //cdatm// version and always get the latest stable version |