graysky2/clean-chroot-manager

Hardcoded pacman.conf paths break chroot build

dschaper opened this issue · 2 comments

If I use hardcoded paths in the pacman.conf file to relocate the metadata for pacman I am unable to build a CCH clean root. I have to comment out the pacman.conf paths and let them use default.

I haven't considered this use case. Can you post the relevant examples from your pacman.conf here?

It actually will break with the stock directories:

[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
RootDir     = /
DBPath      = /var/lib/pacman/
CacheDir    = /var/cache/pacman/pkg/
LogFile     = /var/log/pacman.log
GPGDir      = /etc/pacman.d/gnupg/
HookDir     = /etc/pacman.d/hooks/
#HoldPkg     = pacman glibc