Repository navigation
fix(linux): remove libfuse2 dependency from AppImages - #1070
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The release workflow selects the pinned AppImage toolset, and no actionable merge-blocking risk remains. The packaged runtime artifact was not independently verified in this inspection. Pre-merge checks |
|
|
Marking ready: we're taking the static runtime (no libfuse2). The update-info hook from #1072 targets .upd_info in both runtimes and passed on a dispatched build of main. |
EtienneLescot
left a comment
There was a problem hiding this comment.
Reviewed: static AppImage runtime (toolset 1.0.3), no libfuse2 on the host; update info still embedded. Thanks @satwiksharma01!
Summary
Linux AppImages use electron-builder's legacy runtime by default, which requires
libfuse2on the host. Select the supportedappimagetoolset1.0.3inelectron-builder.json5to use its statically linked runtime.The existing electron-builder 26.15.3 dependency supports this option. Its static-runtime packaging path still appends the embedded blockmap and generates update metadata.
Related issue
Fixes #736
Type of change
Release impact
Desktop impact
Screenshots / video
No visual change.
Testing
DT_NEEDEDlibraries.libfuse2orlibfuse2t64installed.The runtime smoke test uses a small shell application; a complete packaged OpenScreen desktop launch has not been tested. The supported toolset also uses zstd for normal compression and retains the launcher's user-namespace sandbox fallback.
Summary by CodeRabbit