From 912a87c868dd6f67569cfaba9ce0d9d762278d29 Mon Sep 17 00:00:00 2001 From: Todd Gamblin Date: Thu, 9 Jan 2014 18:06:18 +0100 Subject: Fix docs to account for license header. --- lib/spack/docs/features.rst | 1 + lib/spack/docs/packaging_guide.rst | 1 + 2 files changed, 2 insertions(+) diff --git a/lib/spack/docs/features.rst b/lib/spack/docs/features.rst index 91184a3390..9ccf1a85fc 100644 --- a/lib/spack/docs/features.rst +++ b/lib/spack/docs/features.rst @@ -102,6 +102,7 @@ It typically doesn't take much python coding to get from there to a working package file: .. literalinclude:: ../spack/packages/libelf.py + :lines: 25- Spack also provides wrapper functions around common commands like ``configure``, ``make``, and ``cmake`` to make writing packages diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 75e738efcd..60c15895d1 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -42,6 +42,7 @@ It's probably easiest to learn about packages by looking at an example. Let's take a look at ``libelf.py``: .. literalinclude:: ../spack/packages/libelf.py + :lines: 25- :linenos: Directory Structure -- cgit v1.2.3-70-g09d2