From ee8b4e92836cc52dec873342464d8316800523cd Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Tue, 24 Dec 2019 21:59:57 -0500 Subject: 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 Signed-off-by: Allan McRae --- doc/PKGBUILD.5.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/PKGBUILD.5.asciidoc') 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) -- cgit v1.2.3-70-g09d2