conf files overwritten in chroot

[slmb3]

I set up a chroot env following https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
When creating the chroot, I used custom config files with mkarchroot -C <pacman.conf> -M <makepkg.conf>

• When building a package with makechrootpkg -c -r $CHROOT, makepkg uses my custom config files in the chroot with no issue.
• When building a package with paru -U --chroot=$CHROOT, paru overwrites my config files in the chroot (pacman.conf and makepkg.conf) with those from my system config (/etc/)

Goal: don't have paru overwrite these config files so I can use the ones already existing in my chroot env.

I can workaround the makepkg.conf getting overwritten with --makepkgconf <makepkg.conf> arg with paru command.

But ideally we wouldn't have to re-declare the config file locations every time, and paru should just use the ones existing in the chroot, if available. Or at least paru should have a flag and config to tell it to never copy config files from the system.

[Morganamilo]

What reason in particular do you want in the config that's different from your system's config?

[slmb3]

Building packages for other systems mainly. do you have any better recommendations to accomplish the same?

[Morganamilo]

Not really. If you mean building for a different arch. Well that doesn't really work iirc. Paru always uses the current config as the local repos are needed to pull in aur depends. So it doesn't allow you to specify your own.

[slmb3]

No I mean building for same arch, just different makepkg.conf