From: Henrik.Carlqvist@deadspam.com   
      
   On Sat, 27 Aug 2022 23:36:55 +0100, #Paul wrote:   
      
   > I've thought about it because there are a couple of slackbuilds I submit   
   > to slackbuilds.org; building in a clean chroot would help make sure they   
   > build ok on something less customised than my main install - mainly so I   
   > don't miss dependencies.   
      
   On Sun, 28 Aug 2022 05:58:07 +0000, David Chmelik wrote:   
      
   > Reason is 'clean environment'.   
      
   But then, you somehow need to keep your chroot environment clean. That   
   could be done by reinstalling every time you start to build a new package   
   or possibly with overlayfs. However, keeping a reference installation   
   clean is really easy in a virtualized environment like qemu which has the   
   -snapshot parameter. When qemu is started with -snapshot, no changes are   
   saved to the disk image file, instead all changes are kept only in RAM.   
   The next time qemu is started with the same disk image it will be back to   
   its reference state it got since the last time qemu was run without -   
   snapshot.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)