You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked for similar issues beforehand, but could not find any. I could not add my proposal to any existing issue.
I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.
Feature description
AIL changes the names of the appimage files everytime they are updated. One consequence is that it is not possible to reliably have an appimage running at startup, for instance by adding a command in the Startup Applications program in Ubuntu. It's also impossible to reliably run an appimage from a script.
AIL also seems to change the name of the .desktop files, these cannot be target either.
Could it be possible to have, for each appimage, a stable path that can be executed?
Proposed solution
Simlinks could be used as proxies to the appimages. These simlinks would be updated when the app is updates, but the name of the simlink would be stable.
Alternative solutions you considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Pre-submit checks
Feature description
AIL changes the names of the appimage files everytime they are updated. One consequence is that it is not possible to reliably have an appimage running at startup, for instance by adding a command in the Startup Applications program in Ubuntu. It's also impossible to reliably run an appimage from a script.
AIL also seems to change the name of the .desktop files, these cannot be target either.
Could it be possible to have, for each appimage, a stable path that can be executed?
Proposed solution
Simlinks could be used as proxies to the appimages. These simlinks would be updated when the app is updates, but the name of the simlink would be stable.
Alternative solutions you considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: