Page History

...

Need an environment where "conda-smithy" is installed (we have put this in psrel's conda_build env).   After making changes to versions/sha256/buildnumber, (can be useful to do a "git commit" after this so we get an extra message in the git logs, but not necessary).  Then rerender with "conda smithy rerender -c auto", then push.

Order of the travis builds matters because of dependencies:

• libnl, libnl3, roentdek, amityping, prometheus-cpp, libusdusb4
• rmda-core, epix, lcls2_timetool, cameralink-gateway, lcls2-pgp-pcie-apps
• rogue, xtcdata
• psalg
• psana/psdaq
• ami

If we were in conda-forge officially, they take care of these build-order dependencies (but not the versions/sha256/buildnumber).  They may have a bot that tells you that the version was updated, but we still have to update the version number by hand. We haven't gone the conda-forge route because (1) we don't know how much work it is, and (2) cannot upload source .tar.gz to conda-forge, usually get it from GitHub, but the rogue packages are not public.

To create the environment as psrel:

conda create --name ps-N.N.N env_create.yaml (devel env)

conda create --name ps-N.N.N prod_create.yaml (prod env)