Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/pacman-staging-with-build-support.conf
diff options
context:
space:
mode:
authorBrian Bidulock <bidulock@openss7.org>2017-11-18 22:53:37 -0700
committerErich Eckner <git@eckner.net>2019-04-01 10:20:17 +0200
commit2db6be332e051af47ff9a0c2b7998c284bd4f730 (patch)
tree8a8c91b50b86e778ea27d84aef03fefac4df239f /pacman-staging-with-build-support.conf
parent9eb51aec7f1a25517a7f3c6e836d01c08f172106 (diff)
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-staging-with-build-support.conf')
0 files changed, 0 insertions, 0 deletions