Skip to content

Home

Jump to bottom
Songsheng Tao edited this page May 7, 2020 · 1 revision

Welcome to the xpdAcq wiki!

Release

Release on nsls-ii-forge channel

The nsls-ii-forge is conda channel which can be accessed both inside and outside NSLS-II. If you would like to install the xpdacq in the workstations in NSLS-II, you need to release the package on nsls-ii-forge.

Basically, the method is to submit and merge PR to the xpdacq-feedstock and the package will be built and uploaded by CI automatically.

Please follow the following steps to do that.

  1. Fork the repo xpdacq-feedstock to your github.

  2. Clone the repo to your local. git clone git@github.com:<your github account name>/xpdacq-feedstock.git

  3. Add the remote upstream. git remote add upstream git@github.com:nsls-ii-forge/xpdacq-feedstock.git

  4. Checkout a new branch called 'rerender'. git checkout -b rerender

  5. Edit the conda-build recipe. Usually, you need to edit the recipe/meta.yml. If you are not familiar with conda-build recipe. Please read the introduction.

  6. After you finished the edit, rerender the feed-stock. conda smithy rerender --feedstock_directory . -e recipe/conda_build_config.yaml

  7. After rerender is finished, it should show the command command line hint to commit all changes. Copy that line and run it in terminal. Here is an example of what commit message looks like. The version number will depend on the conda-build, conda-smithy and conda-forge-pinning you used. git commit -m "MNT: Re-rendered with conda-build 3.18.9, conda-smithy 3.4.6, and conda-forge-pinning 2019.09.08"

  8. Push the commit to remote branch on origin. git push --set-upstream origin rerender

  9. Submit a PR to the upstream master. Check if the CI build test passed. If it fails, debug your conda-build recipe and rerender again.

Clone this wiki locally