You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You will get a different ``sha256`` if you paste the other ``tar.gz`` URL
126
-
from the repository but retention of the ``autoreconf()`` implementation
127
-
should allow either to work.
123
+
.. tip::
128
124
129
-
We generally recommend you use the project-prepared archive url instead of
130
-
the ``GitHub``-generated ``Source code (tar.gz)`` url, when available,
131
-
since they are less volatile in the face of GitHub shasum algorithm changes.
125
+
We generally recommend you use the project-prepared archive url, when available, instead of the ``GitHub``-generated ``Source code (tar.gz)`` url since those tend to be less volatile in the face of ``GitHub`` shasum algorithm changes.
132
126
127
+
In this case, that would mean using the ``https://github.com/LLNL/mpileaks/releases/download/v1.0/mpileaks-1.0.tar.gz`` url.
128
+
Since the file has special build customizations, the ``sha256`` is different.
129
+
Key among the changes is the presence of ``autogen.sh``, which is a convenience script projects use to customize their Autotools reconfiguration process.
130
+
Consequently, you would replace the more general call to ``autoreconf()`` here with an invocation of the ``autogen.sh`` script.
131
+
An example of setting up and using such a script can be found in the `sos <https://github.com/spack/spack-packages/blob/develop/repos/spack_repo/builtin/packages/sos/package.py>`_ package.
133
132
134
133
Since we are providing a ``url``, we can `confirm the checksum <https://spack.readthedocs.io/en/latest/packaging_guide_creation.html#checksum-verification>`_, or ``sha256`` calculation.
135
134
Exit your editor to return to the command line and use the `spack checksum <https://spack.readthedocs.io/en/latest/packaging_guide_creation.html#spack-checksum>`_ command:
0 commit comments