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

Package KWIVER executables as an AppImage #1277

Open
Erotemic opened this issue Apr 16, 2021 · 1 comment
Open

Package KWIVER executables as an AppImage #1277

Erotemic opened this issue Apr 16, 2021 · 1 comment

Comments

@Erotemic
Copy link
Member

I recently came across this packaging paradigm called AppImage: https://appimage.org/ and it seems like it may be applicable for KWIVER in order to allow "instant usability".

Essentially the idea is that the entire application is packaged into a single executable format. I don't know the details, but I imagine this means all the shared dependencies are packaged in this file. (This tutorial seems to support that idea: https://docs.appimage.org/packaging-guide/manual.html). This means that a single file can be hosted and distributed to people who want to use the KWIVER command line interface without running into issues with installation permissions, missing dependencies, or needing to build the system. This does also mean that all arrows will likely need to be packaged inside the app-image and external plugins will no longer work.

There are limitations, but I think its an interesting enough use case that I'd bring it up as a feature suggestion and make people aware of AppImage.

@russelldj
Copy link
Contributor

I'm curious if this is at all similar to this external user trying to package TeleSculptor with Flatpak. As I remember it he had a pretty difficult time due to fletch being hard to build in isolation.

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

No branches or pull requests

2 participants