Page History

...

• Checkout the package (remove the ".git" subdirectory because it is large).
• Create .tar.gz file with "tar cvfz epix-quad-1.2.0.tar.gz epix-quad/"
• Copy the .tar.gz to the directory where it can be seen: "cp epix-quad-1.2.0.tar.gz /reg/g/psdm/web/swdoc/tutorials/"
• Compute the sha256sum with "sha256sum epix-quad-1.2.0.tar.gz"
• Put this sha256 in the epix-quad-feedstock/recipe/meta.yaml

NOTE: do not use the "--recursive" option when cloning.  For reasons that are not understood by cpo the checkouts become much larger.  Instead use the following:To generate a small .tar.gz file:

• use the following command to ignore the large git-lfs files when cloning:  "GIT_LFS_SKIP_SMUDGE=1 git clone --recursive git clone git@github.com:slaclab/cameralink-gateway cameralink-gateway-8.2.1 (Note, no --recursive)
• git submodule init
• git checkout v8.2.1
• 2"
• remove the ".git" subdirectory because it is largegit submodule update

The pinning is in conda_build_config.yaml (our packages are towards the end of the file, the conda-forge pinnings are earlier).  The conda forge pinnings are obtained from files like: https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/main/recipe/conda_build_config.yaml.  Valerio wrote a small throwaway python script to take the packages from our environment and them to the conda_build_config.yaml.  This script also pins the low-level underlying packages that conda-forge does not explicitly pin and adds them to conda_build_config.yaml.  This conda_build_config.yaml cannot trivially be used by GitHub actions (because it will pull the latest version from conda-forge) so we are using this file and building locally on psbuild-rhel7 (with infinite time we could write a custom action).

...