From 18fb1695b84248fc75ceb3569ff03cbeca51a620 Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Mon, 15 Feb 2021 22:29:56 +0000 Subject: Seriously rework link processing --- pelican/content/BuildingFromSource.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'pelican/content/BuildingFromSource.md') diff --git a/pelican/content/BuildingFromSource.md b/pelican/content/BuildingFromSource.md index 6d79d7d..e17fc16 100644 --- a/pelican/content/BuildingFromSource.md +++ b/pelican/content/BuildingFromSource.md @@ -20,7 +20,7 @@ code then run make", but the details differ. We check out copies of all the several dozen separate repositories and carefully arrange them in a tree structure which matches the official naming scheme. Yes, really. It's tedious, but we have -[export:/user/sra/build-tools/https-sync-repos.py a script to automate this]. +[a script to automate this](export:/user/sra/build-tools/https-sync-repos.py). Be warned that this script is a kludge which relies on parsing XML from this Wiki; this is nasty, but reasonably stable, because the XML itself is generated by another script. @@ -39,7 +39,7 @@ goo necessary to make the whole thing work. Do `git help submodule` for an introduction to git's submodule mechanism. With this model, one just checks out a copy of -[source:/releng/alpha the superrepository], +[the superrepository](source:/releng/alpha), runs `make` in its top directory, and eventually the complete package pops out the other side. -- cgit v1.2.3