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 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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: