Conversation
doutriaux1
left a comment
doutriaux1
left a comment
There was a problem hiding this comment.
@downiec please make sure we do not need space before =2 and also we need to tag vcs and vcs to some stable versions.,
|
Can anyone give a quick explanation of the meta.yaml.in and meta.yaml.official? These files cant be used by conda directly, so are they being manipulated by Travis or something? @James-Crean @doutriaux1 |
|
@sterlingbaldwin official is the recipe used to produce the official/stable release, just so we easily remember what we used. The ".in" one is the one we used in relation with http://github.com/cdat/conda-recipes to generate the meta.yaml for nightly using correct branch, etc... Also has capabilites for repos with "features" (only vtk-cdat at this point) |
sterlingbaldwin
left a comment
sterlingbaldwin
left a comment
There was a problem hiding this comment.
I think the conda create line needs to install the vcdat package.
scripts/setup.sh
Outdated
|
|
||
| # Create a new one | ||
| conda create -y -n ${CONDA_ENV} -c cdat/label/nightly -c conda-forge -c cdat --file $current_dir/backend/requirements.txt | ||
| conda create -y -n ${CONDA_ENV} -c cdat/label/nightly -c conda-forge -c cdat |
There was a problem hiding this comment.
I think this should read
conda create -y -n ${CONDA_ENV} -c cdat/label/nightly -c conda-forge -c cdat vcdat
There was a problem hiding this comment.
Yeah I think you're right. I went ahead and updated that. Thanks!
4 participants
Updated meta.yaml files to make sure python2 is used in conda environment to avoid run from having python 3. Added Sterling's handy conda_build.sh. Other minor changes and cleanup.