Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Couldn't you just replace the old appimage but have the same file name?
Also: If I (or my aforementioned dad) install an AppImage, that is named "Nextcloud-DesktopClient-4.0.4.AppImage" that sets up its own startup shortcut and so on, and then I download an update (because the program literally asked me to download the new AppImage), and the new file is named "Nextcloud-DesktopClient-4.0.5.AppImage", am I supposed to rename it to 4.0.4 manually? Rubs me the wrong way somehow. Or am I supposed to know to rename it to a version-agnostic filename before first opening it, so I don't break things when it updates weeks down the line? My dad wouldn't think of either of these options by the way.
You totally could, but like in my example in the parentheses, if stuff breaks, you have just killed your working version of a program, so I don't have the balls to do that.