Open mdear opened 8 months ago
I have since resolved the errors shown in the last snippet, yet still observe that even though I can run my AppImage successfully on my ARMv8 target the temporary directory was removed despite setting of the indicated env variable.
Since I see the AppImage unpacks to volatile (likely ephemeral) storage, I considered but ultimately rejected a workaround, reasons given below:
Given that I want the flexibility of an AppImage but the persistence of a locally installed app,
Given that the extraction of the AppImage to volatile storage on our ARMv8 platform based on Yocto Poky Linux appears to be done relatively quickly
Given that our users need the app running as soon as possible after reboot
The benefit to extracting to nonvolatile storage via the --appimage-extract
option and copying into volatile storage for runtime efficiency on every reboot may not be an effective strategy, we may end up just launching the AppImage on startup and letting itself unpack to volatile fast working storage every time.
Apaprently, if the NO_CLEANUP env variable is set, the AppImage infrastructure is supposed to not remove the unpacked files and reuse the existing files.
This is really important as we aim to use AppImage packaging in production deployments where we could manage a single unpacking delay, but do not want this delay each and every time the AppImage is run.
Why does this feature appear not to work?
I did try to build the appimagetool from the latest git repo, but still have not yet succeeded in doing so, so I took latest released binaries.