bryson/pacman
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: clarify the format of a PKGBUILD source fragment

Browse source 
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>
This commit is contained in:
Eli Schwartz 2019-12-24 21:59:57 -05:00 • committed by Allan McRae
parent 435f5fc204
commit ee8b4e9283
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/PKGBUILD.5.asciidoc
View file

@ -488,9 +488,9 @@ The source URL is divided into four components:
*fragment*:: *fragment*::
(optional) Allows specifying a revision number or branch for makepkg to checkout (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 from the VCS. A fragment has the form `type=value`, for example to checkout a
have the format `source=(url#revision=123)`. The available fragments depends on given revision the source line would be `source=(url#revision=123)`. The
the VCS being used: available types depends on the VCS being used:
*bzr*;; *bzr*;;
revision (see `'bzr help revisionspec'` for details) revision (see `'bzr help revisionspec'` for details)