Update README.md
Add note about "install scripts". Fix typo.
This commit is contained in:
parent
fc46eb647a
commit
9b65a218ef
1 changed files with 6 additions and 1 deletions
|
@ -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=<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
|
||||
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue