Page History

...

After creating the package then upload, e.g. with "anaconda upload -u lcls-ii yaml-cpp-0.5.3-h1d15853_72.tar.bz2".  May need to do "anaconda login" (once per year?).

Devel Env Creation

As user psrel, we can create a dev environment with "conda env create --name ps-4.5.12 --file Export the current environment to yml (with includes pinnings).  Then we can do "small tweaks" to versions.  But big version changes will break the solver.  If we have a big change, we have to start from scratch: use /cds/sw/ds/ana/conda2/manage/env_create_pinned_12_21.yml".  Valerio made this file with an editor, after exporting the environment to a yaml file (that includes version info).  He also edits this file in-place to add/remove packages./env_create.yaml in the usual fashion (but use libmamba)

Prod Env Creation

As for the devel env, but with a file like "/cds/sw/ds/ana/conda2/manage/prod_create_pinned_12_21.yml".yml" and when we do "conda create" it will pick up the versions that were specified in the feedstock package conda_build_config.yml.

Disappearing Packages

Sometimes our precise pinned package versions disappear from conda-forge.  In the past when this happened Valerio was able to manually modify the above pinned yaml files to choose a nearby version.  This so far has not broken the fast conda-solver behavior.