Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2019-12-24 21:59:57 -0500
committerAllan McRae <allan@archlinux.org>2020-01-07 11:40:32 +1000
commitee8b4e92836cc52dec873342464d8316800523cd (patch)
tree1ac136f2a1e619b19eb0494f6bbb3d451d76b1c7 /doc
parent435f5fc20484d3728d8877eea15c7a8653da6d10 (diff)
doc: clarify the format of a PKGBUILD source fragment
Currently, it could be misread to say that a fragment is literally 'commit', rather than 'commit=somehash'. Anecdotally this does not seem to be obvious to everyone, and rewording it certainly doesn't hurt. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/PKGBUILD.5.asciidoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/PKGBUILD.5.asciidoc b/doc/PKGBUILD.5.asciidoc
index 3bcf5ed7..c304a20c 100644
--- a/doc/PKGBUILD.5.asciidoc
+++ b/doc/PKGBUILD.5.asciidoc
@@ -488,9 +488,9 @@ The source URL is divided into four components:
*fragment*::
(optional) Allows specifying a revision number or branch for makepkg to checkout
- from the VCS. For example, to checkout a given revision, the source line would
- have the format `source=(url#revision=123)`. The available fragments depends on
- the VCS being used:
+ from the VCS. A fragment has the form `type=value`, for example to checkout a
+ given revision the source line would be `source=(url#revision=123)`. The
+ available types depends on the VCS being used:
*bzr*;;
revision (see `'bzr help revisionspec'` for details)