From f5eab41e741cecff85393c228de1c4e1e63d7649 Mon Sep 17 00:00:00 2001 From: Martchus Date: Mon, 25 Dec 2023 01:04:54 +0100 Subject: [PATCH] Improve a few details in the README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index bfa2b92..90bc591 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ local_mirror = file://$local_db_path ``` The server obviously needs write permissions to add packages to repositories. In my -setup I've just add it as group and set permissions accordingly: +setup I just added it as group and set permissions accordingly: ``` sudo chown -R martchus:buildservice-git $local_db_path @@ -222,14 +222,14 @@ keyserver hkp://keys.gnupg.net #### Notes * Adding the pacman keyring is actually not very useful because we need to check signatures of any upstream project and not just arch devs. -* If "auto-key-retrieve" does not work, use `gpg --recv-key ` as a workaround +* If "auto-key-retrieve" does not work, use `gpg --recv-key ` as a workaround. * Also see http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/ ### ccache configuration To use ccache one can set the ccache directory in the config (`ccache_dir`) and install the package `ccache` (and `mingw-w64-ccache` for MinGW packages) into the chroot. Make sure the user you start the server with has permissions to read and write there. Otherwise the resulting -configure errors can be confusing. Internally the server is mounting that directory like +configuration errors can be confusing. Internally the server is mounting that directory as described in [the wiki](https://wiki.archlinux.org/index.php/Ccache#makechrootpkg). If you want to use the existing `ccache` directory owned by your current user, you could do