From 9b65a218ef2f014f3ec18c98c5c73d99a0a9c68f Mon Sep 17 00:00:00 2001 From: Stephen Seo Date: Tue, 2 Apr 2024 14:38:36 +0900 Subject: [PATCH] Update README.md Add note about "install scripts". Fix typo. --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b5c463e..8aa21b9 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,11 @@ works for me. It always builds in a CHROOT, and it lets the user check the 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=" 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 @@ -53,7 +58,7 @@ The AUR Helper requires several things: - 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