Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running appimages with a stable command (stable path) #623

Open
2 tasks done
ColinMaudry opened this issue Jan 29, 2024 · 0 comments
Open
2 tasks done

Running appimages with a stable command (stable path) #623

ColinMaudry opened this issue Jan 29, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ColinMaudry
Copy link

Pre-submit checks

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant