Telcon: 2017 11 30

Attendees

• Daniel Topa
• Patrick Gartung
• Brian Van Essen
• Omar Padron

Announcements

PRs merged:

• Mention conflicts when "spack install" fails: https://github.com/spack/spack/pull/6436
• Speed up sourcing environment file (setup-env.sh): https://github.com/spack/spack/pull/6312
• New issue template for submitting issues on github: https://github.com/spack/spack/pull/6205
• Fix bug where flags like "-foo x" were not treated as a single unit: https://github.com/spack/spack/pull/6169
  • This does not fix the issue that flags should not be rearranged in general
• Function added to (optionally) convert static (PIC) libs to shared: https://github.com/spack/spack/pull/6092

New Issues of note:

• https://github.com/spack/spack/pull/6512 is fixing a few issues with binary caching
• cannot specify variant=None variant from the command line https://github.com/spack/spack/issues/6426

Discussion

• Brian: PRs are sitting around not being merged

  • How to use PRs before they are merged?
  • How to use an edited Spack?
    • For package.py files you can create a repo: http://spack.readthedocs.io/en/latest/repositories.html?highlight=spack%20repo#
    • For config files:

• Brian: I have a unique packages.yaml that lets me work around particulars with my site installation.

  • How do I share this with others?
  • How do I share this base configuration with others and let them add to it?
    • You can place a config yaml file in etc/spack
    • You can also place it in ~/.spack/linux/
    • Scopes: http://spack.readthedocs.io/en/latest/configuration.html#configuration-scopes
  • How to easily swap between packages.yaml files while keeping the Spack installation the same?
    • Suggestion: search current directory for packages.yaml
    • Spack environments can help: https://github.com/spack/spack/pull/4585

• Brian: developing lbann; made a spack recipe. Either use an internal cmake environment, or use spack setup.

  • developing lbann and using spack to install all dependencies
  • Pass cmake flags from command line into a Spack build (maybe this isn't spack setup-oriented
  • An error wasn't properly reported in spack setup where is was in spack install
  • See: https://github.com/spack/spack/pull/5043

• Brian: 6425 ping

• Daniel: https://github.com/spack/spack/issues/6308