Repository navigation
Replies: 1 comment 1 reply
|
How paru's chroot works paru keeps a pristine chroot in Whether that copy is refreshed is decided here, in if [[ ! -d $copydir ]] || (( clean_first )); then
sync_chroot "$chrootdir" "$copydir" "$copy"
fi
So If you also want nothing left behind: [bin]
ChrootFlags = -T
The rest of your config
|
Uh oh!
There was an error while loading. Please reload this page.
Hi.
When using Paru, does it always clean its chroot build (
/var/lib/aurbuild/x86_64/) before building a new package?I am trying to make it as "clean as possible" so whenever Paru builds a new package it always starts fresh/clean, and leaves the minimum amount of cached files on the system, but this may be a dumb concept I am going for.
This is what I am using:
(defaults)
I am new to the concepts of chroots, but cleaning the entire chroot before a new build seems to be a common and right (?) thing to do.
I am especially interested to know if
ChrootFlags = -cmakes sense or is just dumb.Thanks.
All reactions