From bdeb3ed6d0f0654d84ccbac27637e5e89069c55a Mon Sep 17 00:00:00 2001 From: Todd Gamblin Date: Sun, 12 Nov 2023 15:12:33 -0800 Subject: [PATCH] Replace erroneous markdown links w/RST (#315) --- tutorial_binary_cache.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tutorial_binary_cache.rst b/tutorial_binary_cache.rst index b9ad335aa..2c37100f0 100644 --- a/tutorial_binary_cache.rst +++ b/tutorial_binary_cache.rst @@ -20,9 +20,9 @@ binary caches allow you to install pre-compiled binaries to your spack installation path. Together, these two features can speed up builds when using spack within a larger development team. -We will use the filesystem for the mirrors in this tutorial, but -mirrors can also be setup on web servers, in s3 buckets or even in [OCI -registries](https://spack.readthedocs.io/en/latest/binary_caches.html#oci-docker-v2-registries-as-build-cache). +We will use the filesystem for the mirrors in this tutorial, but mirrors can also be +setup on web servers, in s3 buckets or even in `OCI registries +`_. By default, Spack comes configured with a source mirror in the cloud to increase download reliability. We've also already set up a mirror @@ -124,7 +124,7 @@ binary caches as a way of solving this issue. A spack binary cache is made up of spack binary packages. Each spack binary package, ending with a ``*.spack`` extension, is a tarball of an -installed spack package signed with a [gpg signature](https://www.gnupg.org). +installed spack package signed with a `gpg signature `_. When you install a package from a mirror with a binary cache, spack * Checks to see if there is a spack binary package that exactly