summaryrefslogtreecommitdiff
path: root/pacman-gnome-unstable.conf
diff options
context:
space:
mode:
authorBrian Bidulock <bidulock@openss7.org>2017-11-18 22:53:37 -0700
committerErich Eckner <git@eckner.net>2019-01-31 09:59:56 +0100
commitbf6555aa3469e5b289888b5e4fcb3d369eccafa8 (patch)
tree0df851f8b074bbe5596fb76ec165a74d0716d0c2 /pacman-gnome-unstable.conf
parente5d0876a495cd12c15dd3dcee35fccdcab9a111b (diff)
downloaddevtools32-bf6555aa3469e5b289888b5e4fcb3d369eccafa8.tar.xz
arch-nspawn should not take pacman cache from host
Previously, arch-nspawn was using the hosts' pacman cache in the chroot even when the chroot was set up with a different cache by mkarchroot, unless specified with the -c flag. Problem is that makechrootpkg passes no -C, -M nor -c flags to arch-nspawn, so all values must be obtained from the working directory. This change take the cache directories from the pacman.conf specified with the -C option unless the -c option was given (as is the case when the chroot is set up with mkarchroot), and, when neither -C nor -c is given (as is the case when invoked by makechrootpkg), the cache directory is taken from the pacman.conf in the working directory. This wasn't such an issue when i686 was mainline, however, which building packages in a chroot against archlinux32 on an x86_64 platform, the cache of the host should _never_ be used.
Diffstat (limited to 'pacman-gnome-unstable.conf')
0 files changed, 0 insertions, 0 deletions