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. --- doc/makepkg-template.1.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/makepkg-template.1.txt b/doc/makepkg-template.1.txt index 03b2a38..99637d4 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: -- 2.4.2