-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Request: Use fuse3 compatible appimagetool. #563
Comments
I've noticed this project before and had plans to migrate to this tool. But at that time, |
In fact linuxdeployqt only in these lines, so you can update these codes: qBittorrent-Enhanced-Edition/.github/workflows/build_appimage.sh Lines 352 to 499 in 8df67d0
|
I try to switch to First this does not support
I use this command: $ export QTLIB=/usr/lib/Qt-6.7.2
$ export APPIMAGE_EXTRACT_AND_RUN=1
$ ./appimagetool-833-x86_64.AppImage deploy /tmp/qbee/AppDir/usr/share/applications/org.qbittorrent.qBittorrent.desktop
$ ARCH=x86_64 VERSION=1.0 ./appimagetool-833-x86_64.AppImage /tmp/qbee/AppDir/ |
Hey you caught me right before I go sleep, I will reply better later in about 8 hours. But if I didn't read anything wrong. I don't try to use go-appimage to deploy, I only use its appimagetool instead. I still use linuxdeploy to make the appimage, just that I remove the EDIT: Here is an example of what I mean linuxdeploy is still being used. |
Alright here is the changes that I mean, I have not tested it:
Something I'm not sure is if doing this would break the zsync updates. |
Yes. This should break the zsync. And I don't think we should easily migrate to go-appimage now. Since go-appimage does not support like linuxdeployqt features: probonopd/go-appimage#291 |
Yeah I understand that go-appimage isn't ready yet. It's a shame the other method breaks zsync. |
@Samueru-sama linuxdeploy is not linuxdeployqt. While linuxdeployqt is deprecated, linuxdeploy and go-appimagetool are its successors and both maintained. |
Hi, sorry but I'm not sure why you told me that 😅 Also while linuxdeploy is still being maintained it still makes an appimage with the runtime that depends on libfuse instead of the static one which is the reason I opened this issue. Although anyway, I've recently put making PRs migrating appimages to the new runtime due to this bug in the static runtime. |
Change of plan, now appimagetool uses the static runtime by default as well, so it should be easy to use it without breaking zsync, as the zsync flag would be used in appimagetool instead of linuxdeploy-qt. EDIT: NVM, just noticed that the workflow that builds the appimage is a different one lol. |
Edit: It ended up being the changes I did, turns out that linuxdeployqt needs the |
Hey, sorry for the very late reply, I was pretty busy the last days.
I'm sorry for the comment. I just fount this though a linked issue and skipped over this, and assumed you didn't know the difference as you were only talking about -qt before and said people are still using linuxdeploy. But yeah, I'm sorry for that. But yeah, thanks for noticing and doing this. Although I hope that linuxdeploy will be updated accordingly. |
Suggestion
https://github.com/probonopd/go-appimage
I normally would make the PR with the changes, but I noticed your CI is quite complex. 👀
Use case
Fixes a common issue with ubuntu and some forks where libfuse2 no longer comes installed.
This is a problem because ubuntu doesn't let you have both libfuse2 and libfuse3 installed together, even though it is fully possible and distros like arch let you do it.
This appimagetool also uses a zstd compression, which results in a slightly smaller appimage. It also works if the distro only has libfuse2 installed.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: