Make the appimage be able to work with libfuse3 #298
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It uses this version of appimagetool instead because the built in one of linuxdeploy still depends on fuse2: https://github.com/probonopd/go-appimage
Note that I went and also did the --appimage-extract for the appimagetool like you were doing it with linuxdeploy, I don't think it is needed anymore because that appimagetool itself also works with fuse3, but I didn't test the script with podman so I can't be 100% sure.
One potential breaking change is that the appimage will have a different name, because this version of appimagetool requires one to provide the version of the app to add it to the title of the resulting AppImage.