linuxdeployqt VS AppImageUpdate

The second reason is the "modularity" of Arch, why Debian packages all the dependences in many different packages? Because a developer can isolate a bug or exclude that package using the right patch. Arch tends to package everything together. That's why an AppImage of Chromium for me is about 140 MB from a Ubuntu base and 280-300 from an Arch-base... but at least this is an issue of both arch-deployer and arch2appimage... I think that by using linuxdeployqt would be better in this case (SPOILER, it requires the host system with an old GLIBC version, also Debian Bookwork is too new for it xD ).

Eagle uses 'linuxdeployqt' for cross-platform installations. Read about it HERE. There is a qt.conf file in the directory where the eagle executable is located. I am not sure exactly how to use it.

linuxdeployqt allow to automatically pack all shared library that we need on binary file into single AppImage file, although linuxdeployqt mainly to generate AppImage for Qt application but it can use for general application, more information on https://github.com/probonopd/linuxdeployqt.

For raspberry on the other hand is an entirely diferent story. I tried to use this: probonopd/linuxdeployqt but with no avail. The problem is that if i download the AppImage directly from the github account i cannot use it in the raspberry because it is not compiled for raspbian or i was told. So, i tried downloading directly the source code and compile it using the Qt Creator on the raspberry but also i am encountering several problems. When i try to build qt creator gives me this error: MakeFile:65: sub-QtWebEngineApplication-qmake_all] Error 3. Also, i am receiving Unkown module(s) Qt:webengine in the Qt Creator.

You are looking for the windows equivalent of Mac DMG format, or linux appimage https://github.com/probonopd/linuxdeployqt/ / Flatpak.

# Generated by linuxdeployqt # https://github.com/probonopd/linuxdeployqt/ [Paths] Prefix = ../ Plugins = plugins Imports = qml Qml2Imports = qml

I am trying to use linuxdeployqt to create an appimage.

There's an updater for appimages https://github.com/AppImageCommunity/AppImageUpdate

AppImages can contain update information (and even support partial updates using zsync), check out https://github.com/AppImage/AppImageUpdate.

https://github.com/AppImage/AppImageUpdate this only works if the application has information regarding where to fetch the update from...

It would be very nice and handy if we could easily update Tutanota Linux desktop app. Luckily, since it is packaged as an AppImage, there's an easy-to-integrate utility available just for that.

It's not centralised, not like Snap with SnapCraft, not even like Flatpak with it's 'not technically but kinda is in practice' Flathub repository. Anyone can make an AppImage, anyone can host an AppImage, anyone can download and run an AppImage, anyone can implement AppImage integration in a distro, and there's even a nice system for automatic updates for AppImage which again is nicely decentralised.

Some have built-in. some not. Btw I considered AppImageUpdate , but it would become re-install a full new app

The fact is that the delta update system via Zsync and appimageupdatetool are real solutions to the problem, but too many developers do not implement it in their AppImage, myself included.

Btw, regarding Flatpak, I've had multiple issues related to mouse cursor, fonts, and local folder access - all related to the sandboxing of apps, all resolvable, but potentially a problem for a non-technical user. I've had much better experiences with AppImages, but I don't know if they have a graphical app store like interface; even the AppImageUpdate idea is still catching on.