Revisor tends to clean up after itself by default. If a product compose succeeds, you (probably) don't need to change this default behaviour. However, by default, Revisor tends to leave the YUM cache directories untouched. This is to prevent you from having to download all the packages a second, third or more times when you run another compose.
To change this default behaviour, Revisor has an option --clean-up
. The default value for this option is 1
, meaning Revisor will clean up it's temporary, compose-specific files, but no files that could be re-used. Specifying --clean-up=0
will cause Revisor to leave everything behind and not clean anything up at all. This is most ideal for troubleshooting purposes, where one needs to examine the temporary, compose-specific files and see what went wrong. To clean up everything however, because for example you might be low on disk-space, use --clean-up=2
. Revisor will then also clean up the files that could be re-used.
8.7.1. Exception to the Rule
There's one exception to the rule of cleaning up. /var/tmp/revisor/
, or put more accurately, the path specified as the installroot
in the YUM configuration file configured with the model used to compose the product, will not be cleaned up afterwards. When composing live media, this directory may still be in use as a mount-point for the live media filesystem. Removing this directory recursively in these cases would not make sense.