-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Telcon: 2012 02 09
Peter Scheibel edited this page Feb 9, 2021
·
12 revisions
Starting 8am PST February 9th
-
SDK Packages: some downloads of packages may come with bundled 3rd-party libraries that are not possible to separate out
- e.g. a package might try to compile its own hwloc (
mpichormvapichis an example of this) - We'd like a way to designate that when you retrieve a specific package that it "comes with" another package (in the
mpichcase this would avoid building two separate instances ofhwloc)
- e.g. a package might try to compile its own hwloc (
-
Compilers as dependencies: when can you have a virtual dependency on C++ etc.?
- Separate concretization of build deps is a prerequisite
- A few months is expected
- We aren't sure if it will be 0.17
-
When will it be possible to disable user configuration?
- Anticipated for 0.17
- Ideally the user could skip using the config in
~with something likespack --skip-user-config install... - This would be easy but I (Peter) would like doing this after https://github.com/spack/spack/pull/11871 (which is related)
-
Brian VE: want something similar to
spack build-env...but aware of the concretized specs in your environment- Without that, you may have trouble providing the exact spec to
build-env - Or... would it be possible to tell an environment that you want to add build deps to PATH
- Without that, you may have trouble providing the exact spec to
-
Brian VE: a user does
spack uninstall foo@develop, but it isn't actually uninstalled; when the user reinstalls it in the environment, it is added back. They wanted to install the latest commit on thedevelopbranch.