-
Notifications
You must be signed in to change notification settings - Fork 17
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
Devops/docker envs #271
Devops/docker envs #271
Conversation
v2024.01.1 Patch Release
… to ubuntu20.04; copying x86_64 to generic dir; Adding concretizer options for generic architecture targeting w/docker builds.
…generating our host-config file.
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.
Looking good
if sexe("{0} dev-build --fresh --quiet --deprecated -u initconfig {2}@develop%{3} 2>&1 | tee -a \"dev-build-{3}-out.txt\"".format(spack_cmd, os.getcwd(), package_name, s), echo=True) : sys.exit(1) | ||
|
||
# Install only the dependencies for Spheral | ||
if sexe("{0} install --fail-fast --fresh --deprecated --only dependencies {2}@develop%{3} 2>&1 | tee -a \"dev-build-{3}-out.txt\"".format(spack_cmd, os.getcwd(), package_name, s), echo=True) : sys.exit(1) |
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.
Why wasn't this install call needed before?
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.
dev-build
acts the same as install
in regards to concretizing and installing dependencies, but dev-build
doesn't have the --fail-fast
option. So here we have spack install only the dependencies with install
, then let it create the host-config
file from dev-build
with our local repo. Using install
tries to pull spheral develop and that isn't what we want for tpl-manager
Summary
This PR is a refactor
It does the following:
x86_64/packages.yaml
path toUbuntu20.04/packages.yaml
since that is the operating system the file is configured for.generic/
directory for external users to modify for their systems.generic
config files for a system.spack arch -o
to determine operating system and version string when$SYS_TYPE
is not availableAdditional Changes:
<install_prefix>/lib/pythonX.Y/site-packages/Spheral
. This is standard practice for python library install structures. I Also ran into a bug where my filesystem on MacOS would confuse theSpheral/
dir and thespheral
executable file in our installation dir.Docs: https://spheral.readthedocs.io/en/devops-docker-envs/index.html
ToDo :
RELEASE_NOTES.md
with notable changes.