Want To Update Your AppImages? Try These Tools! DistroTube
video description
Date: 2022-03-30
Related videos
Comments and reviews: 10
Alexandre
0:49 GUI to manage updates (Trust, the update isn't a problem anymore)
1:22 Remember: Put all the stuff in -/Applications
1:52 Launch of AppImageUpdate GUI
2:22 Little note about AppImage
2:58 Example of an unupdatable app
4:34 GUI limitations (Dont rush, get it one by one)
5:16 CLI to manage the whole update thing (Again, use .AppImage format)
5:38 CLI launch
6:39 Think twice before updating -Element-
7:00 1st try to update all using the CLI - 7:32 2nd try
7:16 The reason why you shouldn't CTRL+C an update
7:28 Poor Element ... Rest in peace
7:51 Just kidding ... Elemente still remain haha
reply
0:49 GUI to manage updates (Trust, the update isn't a problem anymore)
1:22 Remember: Put all the stuff in -/Applications
1:52 Launch of AppImageUpdate GUI
2:22 Little note about AppImage
2:58 Example of an unupdatable app
4:34 GUI limitations (Dont rush, get it one by one)
5:16 CLI to manage the whole update thing (Again, use .AppImage format)
5:38 CLI launch
6:39 Think twice before updating -Element-
7:00 1st try to update all using the CLI - 7:32 2nd try
7:16 The reason why you shouldn't CTRL+C an update
7:28 Poor Element ... Rest in peace
7:51 Just kidding ... Elemente still remain haha
reply
Voxel
Have you ever experienced the convenience of automatic flatpak updates and GNOME software integration on Fedora? That is how updates should work, not the way you just showed off. The graphical tool needs to be run on each file individually, even with the cli-tool, you have to remember to run it from time to time, you have to use a terminal, and then it turns out only some of your AppImages actually support updates. That is neither convenient, nor is it friendly to users who might be newer to Linux or just don't want to mess with the terminal, so it's clear to me why flatpak is winning since it has none of these issues.
reply
Have you ever experienced the convenience of automatic flatpak updates and GNOME software integration on Fedora? That is how updates should work, not the way you just showed off. The graphical tool needs to be run on each file individually, even with the cli-tool, you have to remember to run it from time to time, you have to use a terminal, and then it turns out only some of your AppImages actually support updates. That is neither convenient, nor is it friendly to users who might be newer to Linux or just don't want to mess with the terminal, so it's clear to me why flatpak is winning since it has none of these issues.
reply
itech
I like appimages, but I don't see them as a replacement for other packaging formats. I think app images shine for simple programs which I wouldn't care if they weren't updated to the latest version, and are meant to be portable, like Balena etcher, so I can put the appimage on an USB and it will always be there. They can totally coexist with other packaging formats because they satisfy a different need, but trying to make it your only way to get software seems pointless to me, of course you can make it work if you want. But I don't think it's worth it.
reply
I like appimages, but I don't see them as a replacement for other packaging formats. I think app images shine for simple programs which I wouldn't care if they weren't updated to the latest version, and are meant to be portable, like Balena etcher, so I can put the appimage on an USB and it will always be there. They can totally coexist with other packaging formats because they satisfy a different need, but trying to make it your only way to get software seems pointless to me, of course you can make it work if you want. But I don't think it's worth it.
reply
thierry
For me the fact that Appimage do not automatically updates is its greatest strength. Stop thinking about you and only to your own computer, we geeks people. I also prefer autoupdates for myself, but think about real life people (the most people!). How many times i heard in my family or colleagues at work talking shit about a new msoffice release. I see many ms office 2007 for example because they cant stand new versions. Appimages are perfect for them because there apps will not change, whereas their core system will.
reply
For me the fact that Appimage do not automatically updates is its greatest strength. Stop thinking about you and only to your own computer, we geeks people. I also prefer autoupdates for myself, but think about real life people (the most people!). How many times i heard in my family or colleagues at work talking shit about a new msoffice release. I see many ms office 2007 for example because they cant stand new versions. Appimages are perfect for them because there apps will not change, whereas their core system will.
reply
Ivan
to update an AppImage there are several ways, not just appimageupdate, you can run the zsync file often provided near the AppImage itself or maybe you can write a script that can check if the name and/or number of the installed version is still on the main page of a website or repository, and if -yes- then download and replace it. All the AppImages are updatable this way. This is the way AM and AppMan can update the programs they can manage, I invite you to take a look to these two tools.
reply
to update an AppImage there are several ways, not just appimageupdate, you can run the zsync file often provided near the AppImage itself or maybe you can write a script that can check if the name and/or number of the installed version is still on the main page of a website or repository, and if -yes- then download and replace it. All the AppImages are updatable this way. This is the way AM and AppMan can update the programs they can manage, I invite you to take a look to these two tools.
reply
Paul
My comment in the last video about FreeCAD daily appimages actually involved appimage-update. It was the recommended method to update the FreeCAD appimage.
It failed most of the time.
My other experience with updating appimages was with a Tutanota email appimage that had a built in update facility and that was very good.
I use Prusaslicer appimage and that's ok because it's a small image and they don't update that too frequently.
reply
My comment in the last video about FreeCAD daily appimages actually involved appimage-update. It was the recommended method to update the FreeCAD appimage.
It failed most of the time.
My other experience with updating appimages was with a Tutanota email appimage that had a built in update facility and that was very good.
I use Prusaslicer appimage and that's ok because it's a small image and they don't update that too frequently.
reply
Penguin
This is kind of a hacky and wonky solution and it depends on the developer to add update information into the appimage which might be a lot of them, but you did show an example where it didn't work. With snaps all you have to do is -sudo snap refresh- and everything updates if there are new versions in the repository. much more seamless and user friendly.
Sorry appimage is still not better than snap.
reply
This is kind of a hacky and wonky solution and it depends on the developer to add update information into the appimage which might be a lot of them, but you did show an example where it didn't work. With snaps all you have to do is -sudo snap refresh- and everything updates if there are new versions in the repository. much more seamless and user friendly.
Sorry appimage is still not better than snap.
reply
tn5421
At first, I didn't like that they didn't integrate into the system very well. Then, AppImageLauncher was written.
Then, I didn't like that I had to manually manage updating all of my programs. Now, there is AppImageUpdate.
Once that gets some more work and most AppImages work with it, then AppImages will be equal to, if not superior to, Flatpaks.
reply
At first, I didn't like that they didn't integrate into the system very well. Then, AppImageLauncher was written.
Then, I didn't like that I had to manually manage updating all of my programs. Now, there is AppImageUpdate.
Once that gets some more work and most AppImages work with it, then AppImages will be equal to, if not superior to, Flatpaks.
reply
Lestibournes
Seems to me like the best option would be to have a central AppImage repo and a -package manager- for AppImage that could be used to search, display, install, update, and remove AppImages just like other package manager, but still keep the self-contained standalone single file application format. Then you get the best of both worlds.
reply
Seems to me like the best option would be to have a central AppImage repo and a -package manager- for AppImage that could be used to search, display, install, update, and remove AppImages just like other package manager, but still keep the self-contained standalone single file application format. Then you get the best of both worlds.
reply
RedBearAK
When I started using macOS virtually every 3rd party application available for the platform was already capable of checking for and downloading its own updates through programming frameworks like Sparkle. That was 20 --years-- ago. For it to be this obtuse and unreliable to update AppImages today is deeply embarrassing.
reply
When I started using macOS virtually every 3rd party application available for the platform was already capable of checking for and downloading its own updates through programming frameworks like Sparkle. That was 20 --years-- ago. For it to be this obtuse and unreliable to update AppImages today is deeply embarrassing.
reply
Add a review, comment
Other channel videos
8:58