Left over files on removal (feature request)

[sailfish-containers]

Left over files on removal (feature request)

[Kabouik]

I agree about the .pyc file, but isn't it standard to keep configuration files and data files when uninstalling? pkgbuild even has a macro for configuration files to identify them and protect them from deletion at uninstall. Default configuration files sure should be removed, but all configuration files here are tied to container names, and hence could be considered customized by user (mine is actually customized anyway because I added mount points).

Files in /home/.lxc/ are data files in my opinion, and I'm not sure it would be good to have them deleted with no prior notice at uninstall, people would expect to find them again if they reinstall the application. They would not only lose the data they have in the container, but everything they set up, installed and configured too. To me the rootfs in /home/.lxc/ are pretty much like .img or .vbox files for VMs, they should persist even if the VM application is uninstalled.

However I agree that scripts/buttons to help cleaning for anyone wanting a full uninstall could be useful. I believe the Settings > Destroy container button is already doing that for /home/.lxc/containername, but it will work only for containers listed in the application, and hence would probably not be possible if the corresponding configuration file in /var/lib/lxc/ has already been removed or moved. Actually, does the Destroy button delete the configuration file too? I didn't test that.