Skip to content

"AM" 6.10.1
Compare
Choose a tag to compare
@ivan-hc ivan-hc released this 06 Jun 15:07
· 2016 commits to main since this release
6.10.1
ce9bbbd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Improved the option "-c" or "clean"

I assume you all know the difference between "AM" and "AppMan".

The other evening I updated my Chromium AppImage, and after installing it with the command appman -i chromium and after isolating it with the command appman -H chromium not to dirty my $HOME directory with its dotfiles (see module "sandboxes.am"), I finally ran the command appman -f to check if the version that appeared was ok, and... I noticed that the installation had reached 200 MB while it should be ust 140 MB instead. The issue here were that the dotfiles had been distributed in the "chromium.home" directory previously created with the option -H, so the ".cache" directory created inside it was filled, making the whole installation of the AppImage look larger than it should.

From this episode I decided to extend the "-c" option also to all the "*.home/.cache" directories near the installed AppImages, if they exist. And I didn't just add this:

  • as I've already said above, now this option will clean *.home/.cache directories of AppImages created with the option -H;
  • unnecessary operations are hidden if dedicated files and directories are not in place, as was already the case for cleaning of orphan launchers created with the option --launcher;
  • all deleted files from the "modules" directory will be listed one by one;
  • also, the cleaning process is faster, almost instantaneous.

Here is a test I've done with both "AM" and "AppMan", by adding a .home directory in Chromium (for AppMan) and Avidemux (for "AM") and some random files in the "modules" directory of "AM":

simplescreenrecorder-2024-06-06_16.40.45.mkv.mp4

Full Changelog: 6.10...6.10.1

Assets 2
Loading