-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rework yum-requirements #1019
rework yum-requirements #1019
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,6 +39,9 @@ mkdir -p "$ARTIFACTS" | |
DONE_CANARY="$ARTIFACTS/conda-forge-build-done-${CONFIG}" | ||
rm -f "$DONE_CANARY" | ||
|
||
# Set up the docker image that we are going to use. | ||
{{ docker.executable }} pull $DOCKER_IMAGE | ||
|
||
{%- if docker.interactive is defined %} | ||
{%- if docker.interactive %} | ||
# Enable running in interactive mode attached to a tty | ||
|
@@ -53,15 +56,17 @@ DOCKER_RUN_ARGS=" -it " | |
|
||
export UPLOAD_PACKAGES="${UPLOAD_PACKAGES:-True}" | ||
{{ docker.executable }} run ${DOCKER_RUN_ARGS} \ | ||
-v "${RECIPE_ROOT}":/home/conda/recipe_root:ro,z \ | ||
-v "${FEEDSTOCK_ROOT}":/home/conda/feedstock_root:rw,z \ | ||
-e CONFIG \ | ||
-e BINSTAR_TOKEN \ | ||
-e HOST_USER_ID \ | ||
-e UPLOAD_PACKAGES \ | ||
$DOCKER_IMAGE \ | ||
{{ docker.command }} \ | ||
/home/conda/feedstock_root/${PROVIDER_DIR}/build_steps.sh | ||
-v "${RECIPE_ROOT}":/home/conda/recipe_root:ro,z \ | ||
-v "${FEEDSTOCK_ROOT}":/home/conda/feedstock_root:rw,z \ | ||
-e CONFIG \ | ||
-e BINSTAR_TOKEN \ | ||
-e HOST_USER_ID \ | ||
-e UPLOAD_PACKAGES \ | ||
$DOCKER_IMAGE \ | ||
{{ docker.command }} \ | ||
/home/conda/feedstock_root/${PROVIDER_DIR}/build_steps.sh | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also are we able to revert the changes here too? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we could, but this is just whitespace There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Exactly |
||
|
||
|
||
|
||
# verify that the end of the script was reached | ||
test -f "$DONE_CANARY" |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
**Added:** | ||
|
||
* <news item> | ||
|
||
**Changed:** | ||
|
||
* Changed how yum_requirements.txt is used in the docker build. It now installs the yum_requirements | ||
prior to doing the primary conda build without needing to use sudo. | ||
|
||
**Deprecated:** | ||
|
||
* <news item> | ||
|
||
**Removed:** | ||
|
||
* <news item> | ||
|
||
**Fixed:** | ||
|
||
* <news item> | ||
|
||
**Security:** | ||
|
||
* <news item> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you update this comment or remove it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually are we able to just revert all of the changes to this file now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could, though this does add the advantage that we dont need a rerender if we've changed yum_requirements, and it simplifies
configure_feedstock.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is roughly how I proposed
yum_requirements.txt
originally ( #135 ), but Phil made a compelling argument that they should be listed explicitly ( #134 ). Ultimately I don't feel strongly either way, but it seems the crux of the needed change is quite simple; so, it would be nice if this PR reflected that. Orthogonal changes are better left for other PRs IMHO.