-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
I made a to-do list to maintain appimage.github.io #3112
Comments
Why do you think the AppImages in your "Delete in list" should be deleted? I strongly disagree. They have been available in AppImage format, and those AppImages are still usable and hopefully will be forever. If AzPainter, just to pick one example, any less good an application just because it doesn't need constant updates? For me, it actually makes it a better application, because it doesn't need constant updates anymore. One key point of the AppImage format is that applications in this format will run forever (if you archive the AppImage alongside a compatible Live ISO of the operating system). Unlike the stuff that is in repositories, where versions come and go, and a couple of years down the road you may have trouble getting old versions to run. So, let's not delete anything. Except it is known malware, no longer downloadable anywhere, etc. |
Most of the list is either unavailable or new versions are no longer shipping as Appimage. AppImage is an unchanging container - which can only be rebuilt according to the code base of the po itself. If the software itself "rots", so does AppImage, in which case, it may not run for all users. For example, in preparation of this to-do, yesterday I did not start blubvolley which requires gtk2-x11.
As for azpainter: we have a note from the author: "Important note: Continuous AppImage-builds are not yet usable. Currently they're used only for testing purposes!". azpainter itself is built in appimage format via travis-ci, the last build was buggy on July 2, 2021. As of June 15, 2021 travis-ci.org was replaced by travic-ci.com |
So? You boot a distribution that comes with gtk2-x11 and can still run it there. Will forever be able to. Just because there are no newer versions of an application doesn't mean that it stops working. In fact, some of the best applications are no longer updated. You just need to run them on an operating system Live ISO from the same time. Again, my philosophy is: Once an application enters this list, it will never leave the list; only exceptions: malware and the like. |
The first 3 applications are not available as AppImage, in 4 the application is not multilingual. There are also applications like Mira from boox.com, uarmstudio which are meaningless without proper hardware |
At least at the point in time when they entered the repository, they had an AppImage available, because it needed to pass the test to go in. We should follow up with the authors, asking them where the AppImages went.
That is not a requirement.
What do you mean by that statement? Would you not want to have them listed just because they require special hardware? Heck, with that excuse you could remove all 3D printer slicers, because you need a 3D printer to make use of them. That you need special hardware to use them is no reason to remove AppImages. |
I wanted to say that it is a bit strange: AppImage allows you to download and run a single file (at least that is what I understand the intent) while there is a sheet of this software. If, I understand correctly, the purpose of which is to simplify the search for a certain one. But when you buy a certain hardware you are more likely to look for software for it on the official site of the product, not in this list. On the other hand the user who downloads this application cannot use it if he has special hardware |
Well. I can say that more than once I have bought some piece of hardware because there was software for it in the AppImage format. Expensive hardware, even. |
Hi there. I develop an application that's in the to be deleted list :) It must be a lot of work to maintain an index of all the software which provide AppImages .. it would be good ideally to keep referencing all the projects that still provide a working AppImage. However if the download links don't work or aren't up-to-date, shouldn't it be the software author's responsability to provide the correct links via a PR ? Unless a project stops using AppImages i think it should be kept in the list. Will make a PR, sorry. |
I checked now, earlier the site and the download link did not work for me, and there was no appimage in github / github, I assumed that you do not provide it
Author doesn't always know about this sheet, their program is added automatically or by a volunteer. Therefore, volunteers try to keep the list up to date for programs that will scrape this list so that everything works for the end user. |
I build AppImages with GitLab CI and store them in IPFS. Will make PR today to provide a download link using an IPFS HTTP gateway. |
Add in list
Update links
Delete in list
The text was updated successfully, but these errors were encountered: