Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add option to wrap AppImage in tarball
See original GitHub issueIt would be nice if we could configure electron-builder to automatically pack any AppImage releases in a tarball. This has two advantages:
-
Users don’t have to manually make
.AppImagefile executable. Instead they can simply run it after extracting it from the tarball. -
The archived
.AppImagefile could have a more user-friendly name likeproductNameinstead of{name}-{version}-{arch}while the tarball file name could still contain all the relevant information to identify a release.
E.g. you could distribute a my-app-1.0.0-linux-x64.tar that, when extracted, produces MyApp.AppImage that can be run without any additional steps. Essentially this would be analog to distributing .app folders as .zip archives on OSX.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:21 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Publishing both is an option of course.
I can see why it might be bad for 2GB apps. But mine is 80MB or so. Also I still publish an AppImage (for auto update, etc), I just provide a tar for the first download. 'cause automatic or not, unpacking is still a way more familiar action for regular users, than changing a permission. Even advanced users get confused initially (I mean I’m not guessing here, I’ve seen it happening every time).