Closed andfoy closed 3 years ago
There seem to be changes to existing CDTs in this PR that should not have happened.
@beckermr, I was wondering why there were so many changes on other CDTs, I just followed the instructions listed on the README over the changes of 14a14251e6d435ba959c3861f0ac8cd4fde603c1
Yeah. Don't use the --fast option and make sure your branch is up to date with master.
I will try it locally too.
Should I use the --force
option?
No not yet.
Please see the repo readme for directions on how to make PRs on this repo.
Checklist:
cdt_slugs.yaml
file and you have rerun the scriptpython gen_cdt_recipes.py
.rpm.py
), you have bumped the build number inconda_build_config.yaml
and have remade all of the recipes via runningpython gen_cdt_recipes.py --force
custom: true
in thecdt_slugs.yaml
file.{{ cdt_build_number }}
for old-style/legacy CDTs or{{ cdt_build_number|int + 1000 }}
for new-style CDTslicense_file
key in thecdt_slugs.yaml
file with the path to the appropriate license inlicenses/
NOTE: If you make any changes to
cd_slugs.yaml
, you need to reun the generator code viapython gen_cdt_recipes.py
.