Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWieland Hoffmann <themineo@gmail.com>2015-06-03 11:04:13 +0200
committerAllan McRae <allan@archlinux.org>2015-06-20 17:32:56 +1000
commit0f302df5edf40eabfa28724f8b4e1cc2f3fa176b (patch)
tree96507d60cd73e56ff6014ba72912ea7168f16fa6 /doc
parent3d4529335c598e79b5a483fedc4c9d5c12ef10f1 (diff)
makepkg-template.1: Clarify which file version-less markers use
The old text could be interpreted such that makepkg-template compares the version numbers of the templates to find the most recent one. Rephrase this to make it explicit that "$template_name.template" is used. Signed-off-by: Florian Pritz <bluewind@xinu.at>
Diffstat (limited to 'doc')
-rw-r--r--doc/makepkg-template.1.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/makepkg-template.1.txt b/doc/makepkg-template.1.txt
index 03b2a38e..99637d43 100644
--- a/doc/makepkg-template.1.txt
+++ b/doc/makepkg-template.1.txt
@@ -47,8 +47,8 @@ and end markers and the template code on the first run.
Template files should be stored in one directory and filenames should be
"$template_name-$version.template" with a symlink "$template_name.template"
pointing to the most recent template. If the version is not set in the marker,
-'makepkg-template' will automatically use the most recent version of the
-template, otherwise the specified version will be used. This allows for easier
+'makepkg-template' will automatically use the target of "$template_name.template",
+otherwise the specified version will be used. This allows for easier
verification of untrusted PKGBUILDs if the template is trusted. You verify the
non-template code and then use a command similar to this: