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 then "git commit " after this so we get an extra message in the git logs, but not necessary)-a -m".  Then rerender with "conda smithy rerender -c auto", then push.  Watch the status of the builds at https://travis-ci.com

Order of the travis builds matters because of dependencies:.  These are the waves.

• libnl, libnl3, roentdek, amityping, prometheus-cpp, libusdusb4rmda-core, epix, lcls2, psmon, networkfox, rogue, lcls2_timetool, cameralink-gateway, lcls2-pgp-pcie-apps
• rogue, xtcdata
• , xtcdata
• rmda-core (depends on libnl)
• fabric (depends rmda-core)
• psalg (depends on xtcdata)psalg
• psana/psdaq (depend on psalg)
• ami (depends on psana)

If a package is built for python build matrix tells it to build for the officially supported conda-forge versions (3.6,3.7,3.8).

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.

...