7abc2fb26d
* docbook processing works correctly for gdk-pixbuf 1. The various bits of documentation in gdk-pixbuf include hardcoded references to dtd's and stuff at their canonical, Internet, locations. BUT, gdk-pixbuf runs xslt-proc with the `--nonet` option, which forbids it from using the network. Sadness ensues. Traditionally folks use XML Catalogs to map these to local copies. Our docbook-xsl package wasn't setting the appropriate env var in its dependents environments to use our catalog. Now it does. Less sadness ensues. 2. If we're going to use these things, we should depend on them. * Add gdk-pixbuf's bin to build environment The "post-install.sh" script uses gdk-pixbuf-query-loaders, which was installed earlier. If py-psyclone can set its own bin on its PATH, so can we... * Make gdk-pixbuf use recognizable docbook location Our docbook-xsl package assumes that the canonical location is `http://cdn.docbook.org/release/xsl/current/manpages/docbook.xsl`, but the gdk-pixbuf's meson build script uses `http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl`. This means that our XML Catalog doesn't fix the reference and sadness happens. Just patch the build that we see what we want to see, then we can make it all go away. * Add commentary re docbook patch * Make catalog helper a property Thanks @adamjstewart! * Run tests if/when run_tests is true Thanks @adamjstewart! * Tune up dependencies Thanks @adamjstewart! * Wordsmit commentary
Spack
Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist.
Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.
See the Feature Overview for examples and highlights.
To install spack and your first package, make sure you have Python. Then:
$ git clone https://github.com/spack/spack.git
$ cd spack/bin
$ ./spack install libelf
Documentation
Full documentation for Spack is the first place to look.
Try the Spack Tutorial, to learn how to use spack, write packages, or deploy packages for users at your site.
See also:
- Technical paper and slides on Spack's design and implementation.
- Short presentation from the Getting Scientific Software Installed BOF session at Supercomputing 2015.
Get Involved!
Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.
Mailing list
If you are interested in contributing to spack, join the mailing list. We're using Google Groups for this:
Slack channel
Spack has a Slack channel where you can chat about all things Spack:
Sign up here to get an invitation mailed to you.
You can follow @spackpm on Twitter for
updates. Also, feel free to @mention us in in questions or comments
about your own experience with Spack.
Contributions
Contributing to Spack is relatively easy. Just send us a
pull request.
When you send your request, make develop the destination branch on the
Spack repository.
Your PR must pass Spack's unit tests and documentation tests, and must be PEP 8 compliant. We enforce these guidelines with Travis CI. To run these tests locally, and for helpful tips on git, see our Contribution Guide.
Spack uses a rough approximation of the
Git Flow
branching model. The develop branch contains the latest
contributions, and master is always tagged and points to the latest
stable release.
Authors
Many thanks go to Spack's contributors.
Spack was created by Todd Gamblin, tgamblin@llnl.gov.
Citing Spack
If you are referencing Spack in a publication, please cite the following paper:
- Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. The Spack Package Manager: Bringing Order to HPC Software Chaos. In Supercomputing 2015 (SC’15), Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
License
Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.
All new contributions must be made under both the MIT and Apache-2.0 licenses.
See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.
SPDX-License-Identifier: (Apache-2.0 OR MIT)
LLNL-CODE-647188