I'm thinking about put all temporary files at system stardard path /tmp

[directentis1]

Currently, during install/upgrading apps, am will extract all temps file in current directory of the path of each app.
What if we allow users to specify temp files in a different directory, or use the default Unix path like /tmp/?

Since my appimages are currently located in a path that is fused mounted to a NAS and cloud drive, installing and generating a lot of temporary/auxiliary files is usually quite slow.

I think it would be reasonable if the temporary files during the installation process were located in a different directory and only the final results were moved to the destination directory.
Would that be more flexible?

[Samueru-sama]

The files that get made there are the .desktop and .DirIcon, which we extract only those from the appimage since --appimage-extract supports partial extraction. That is we are never extracting the whole appimage or anything like that.

In other words we are only getting 2 files that are less than 0.1 MIB each, if this is slow, doing it on /tmp will not make it any faster.

And also this only happens during installation, during updates AM will not get the .desktop and .DirIcon, it will only download the appimage and then replace the existing one.

You might want to install appimageupdatetool since this makes updates a lot faster, we have a fork where I posted some simple benchmark showing the bandwidth usage:

https://github.com/pkgforge-dev/AppImageUpdate-Enhanced-Edition?tab=readme-ov-file#appimageupdate-enhanced-edition

If you check the AM-updater scripts for each app, they all first check if you have appimageupdatetool before downloading the entire appimage again.

[directentis1]

Ah, I see most apps working like this.
But there's one that doesn't have the exact common path to the .desktop icon when extracted, or that requires its subfolder to be managed (like Brave or Calibre).
It might just be performance issues when I update all the apps.

[ivan-hc]

Ah, I see most apps working like this. But there's one that doesn't have the exact common path to the .desktop icon when extracted, or that requires its subfolder to be managed (like Brave or Calibre). It might just be performance issues when I update all the apps.

you mean these three https://github.com/ivan-hc/AM/tree/main/appimage-bulder-scripts/x86_64

they are built on-the-fly (for demonstration purposes, because AM can work as an AUR helper, compiling "stuff")

[directentis1]

Calibre for sure, but I think Brave also the case, it's extracted with bundled of files when install.

➜  brave  tree -a | tail -n 5
├── vk_swiftshader_icd.json
├── xdg-mime
└── xdg-settings

75 directories, 172 files

Probably just some exceptions compared to most other cases so I can patch them myself with sed before updating 😄

[ivan-hc]

oh, ok... i understand what your problem is: you installed brave instead of brave-appimage

the brave package is the original version, it is not the AppImage

[directentis1]

Got it!! I'll switch to appimage version to avoid those problems.

That why "brave" has labed as "dynamic-binary".

➜  ~  appman -f | grep "brave" 
◆  brave                  |  1.76.82                |  dynamic-binary  |  389   MiB