From 1bf427c6d726084b2cb724303a9a622938ad7460 Mon Sep 17 00:00:00 2001 From: Martchus Date: Sun, 28 May 2023 20:28:14 +0200 Subject: [PATCH] Improve README section about chroot creation --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ef7c14b..5d181ff 100644 --- a/README.md +++ b/README.md @@ -145,10 +145,13 @@ expects a directory layout like this: So there's a "root" chroot for every architecture and config files for that architecture in dedicated directories. To achieve this one just has to call `mkarchroot` for each architecture. -It is invoked like this: +It is generally invoked like this: ``` -mkarchroot -C /path/to/pacman.conf -M /path/to/makepkg.conf /directory/to/store/the/tree base-devel +cd /the/chroot/directory +mkarchroot -C config-x86_64/pacman.conf -M config-x86_64/makepkg.conf arch-x86_64/root base-devel +sudo vim arch-x86_64/root/etc/pacman.d/mirrorlist # uncomment at least one mirror +arch-nspawn arch-x86_64/root # enter bash shell within chroot ``` Note that `makechrootpkg` will not use the "root" chroot directories directly. It will create a