PKGBUILD (by default) prior to building. There is no automatic dependency
management. That must be done in the config. An example config is provided.
+Note that if a "install=<filename>" is specified in the PKGBUILD, then the
+configured editor will also open the specified file once the PKGBUILD is
+approved by the user. This check is necessary because such "install scripts"
+define hooks that are run when the package is installed.
+
# Things to know before using the helper
Sometimes if a package prompts a user to select between alternate package
- A CHROOT to build in.
- A "checking GNUPG" directory that contains the GPG public keys that will be
checked when building the PKGBUILD.
- - A "singing GNUPG" directory that contains the GPG private key that will sign
+ - A "signing GNUPG" directory that contains the GPG private key that will sign
the built packages and repository database.
- SUDO privileges to be able to use `makechrootpkg`.
- `/etc/pacman.conf` must be configured to use the custom repository's