aboutsummaryrefslogtreecommitdiff
path: root/pelican/content/BuildingFromSource.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2021-02-15 22:29:56 +0000
committerRob Austein <sra@hactrn.net>2021-02-15 22:29:56 +0000
commit18fb1695b84248fc75ceb3569ff03cbeca51a620 (patch)
tree74e8c1473c11ca8db6f942d52acd5743c3e4d17c /pelican/content/BuildingFromSource.md
parentdd255ef58a617214ea3ece613c417af1fc1549ec (diff)
Seriously rework link processing
Diffstat (limited to 'pelican/content/BuildingFromSource.md')
-rw-r--r--pelican/content/BuildingFromSource.md4
1 files changed, 2 insertions, 2 deletions
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.