[pull] master from aurutils:master

Makefile

@@ -7,7 +7,7 @@ ETCDIR ?= /etc
 AURUTILS_LIB_DIR ?= $(LIBDIR)/$(PROGNM)
 AURUTILS_VERSION ?= $(shell git describe --tags || true)
 ifeq ($(AURUTILS_VERSION),)
-AURUTILS_VERSION := 20.5.2
+AURUTILS_VERSION := 20.5.3
 endif
 AURUTILS_LIB := $(shell find lib/ -type f -name 'aur-*')
 

examples/README.md

@@ -111,7 +111,7 @@ clients of the local repository.
 Assuming a list of rebuild targets is known, `sync-rebuild` performs the
 following steps:
 
-1. Retrieve and update all source files with `aur fetch --existing`
+1. Retrieve all source files with `aur fetch --existing`
 2. Retrieve all versions of packages in the local repository
 3. If `pkgver` matches the local repository version, set `pkgrel` in the
    `PKGBUILD` to the local repository version, incremented by `0.1`. Otherwise,
@@ -137,8 +137,8 @@ package. For example:
 aur repo --search '^python.*' --search-by depends --list
 ```
 
-`aur-sync` can be used to inspect new PKGBUILD revisions beforehand
-and retrieve any new dependencies. For example:
+`aur-sync` can be used to retrieve and inspect new AUR revisions, as well as
+retrieve new dependencies for target packages. For example:
 
 ```bash
 aur sync --no-build --no-ver-argv <targets...>

makepkg/aurutils.changelog

@@ -6,6 +6,18 @@
 * `aur-chroot`
   + preserve `LOGDEST` and `SRCDEST` by default (#1196)
 
+* `aur-sync`
+  + pre-process .SRCINFO with `pacini` (#1203)
+
+* `examples`
+  + `sync-rebuild`
+    - use `aur-fetch` instead of `aur-sync`
+    - allow handling multiple targets
+
+* `man1`
+  + documentation updates (#1206, #1207)
+  + add setfacl example (aur-build.1)
+
 ## 20.4
 
 * `aur-build`

man1/aur-build.1

@@ -449,6 +449,22 @@ file with the following contents:
     aurbuild ALL = (root) NOPASSWD: /usr/bin/pacman, /usr/bin/pacsync
 .EE
 .PP
+The following
+.B aur\-build
+options require root access:
+.BR \-\-syncdeps ,
+.BR \-\-rmdeps ,
+.BR \-\-chroot .
+Root access are also required for
+.BR pacsync (1)
+and
+.BR "pacman \-S" ,
+unless the
+.B \-\-nosync
+or
+.B \-\-chroot
+options are specified.
+.PP
 .BR aur\-build (1)
 and related programs such as
 .BR aur\-sync (1)
@@ -458,38 +474,36 @@ user.
 For example:
 .PP
 .EX
-    # cd /var/cache/aurbuild
-    # sudo \-u aurbuild git clone https://aur.archlinux.org/mypackage.git
-    # cd mypackage
-    # sudo \-u aurbuild aur build \-d custom
+    $ sudo -u aurbuild -i
+    $ git clone https://aur.archlinux.org/mypackage.git
+    $ cd mypackage
+    $ aur build \-d custom
 .EE
 .PP
 Any created files in the local repository (such as packages,
 signatures and database files) will be owned by the
 .I aurbuild
 user and group.
 .PP
+To exchange files between the build user and a regular user,
+.BR setfacl (1)
+may be used. For example, assume the directory
+.I /home/custompkgs
+is owned by
+.IR $USER:USER ,
+and that read/write access should be given to the
+.I aurbuild
+user. The following commands set the default permissions for this directory
+and modifies any existing permissions, respectively:
+.PP
+.EX
+    $ setfacl \-dm 'g:aurbuild:rwX' \-Rm g:aurbuild:rwX \-\- /home/custompkgs
+.EE
+.PP
 See also
 .B Avoiding password prompts
 in
 .BR aur\-chroot (1).
-.TP
-.B Note:
-The following
-.B aur\-build
-options require root access:
-.BR \-\-syncdeps ,
-.BR \-\-rmdeps ,
-.BR \-\-chroot .
-Root access are also required for
-.BR pacsync (1)
-and
-.BR "pacman \-S" ,
-unless the
-.B \-\-nosync
-or
-.B \-\-chroot
-options are specified.
 .
 .SS PKGBUILD signatures
 GPG signatures defined in the