stephenseo/AnotherAURHelper
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update README.md

Browse source
This commit is contained in:
Stephen Seo 2022-06-04 17:28:13 +09:00
parent a84be4a980
commit 882096b8c6
1 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -34,7 +34,7 @@ script to run.
Use `/usr/bin/mkarchroot` to create your CHROOT in a directory. Use `/usr/bin/mkarchroot` to create your CHROOT in a directory.
mkarchroot $HOME/mychroot/root base base-devel ccache sccache mkarchroot $HOME/mychroot/root base base-devel ccache sccache cmake ninja
You must refer to the CHROOT as `$HOME/mychroot` if you used the same name as in You must refer to the CHROOT as `$HOME/mychroot` if you used the same name as in
the previous example. the previous example.
@ -49,12 +49,15 @@ GNUPG.
GNUPGHOME=$HOME/myCheckingGNUPGDir gpg --recv-keys A_DEV_KEYS_FINGERPRINT GNUPGHOME=$HOME/myCheckingGNUPGDir gpg --recv-keys A_DEV_KEYS_FINGERPRINT
Note that gpg may not automatically create the GNUPGHOME directory.
### Signing GNUPG ### Signing GNUPG
You will need to set up a GPG public/private key pair. GNUPG always respects the You will need to set up a GPG public/private key pair. GNUPG always respects
`GNUPGHOME` environment variable as the `.gnupg` dir, so set the variable first, the `GNUPGHOME` environment variable as the `.gnupg` dir, so set the variable
then set up your keys. The keys will be used to sign the packages you build and first, create the directory, then set up your keys. The keys will be used to
the custom repository that stores the package metadata. sign the packages you build and the custom repository that stores the package
metadata.
Set the `signing_gpg_key_fp` variable in the config to the output fingerprint Set the `signing_gpg_key_fp` variable in the config to the output fingerprint
from of: from of: