❤️ lieselotte
I somehow knew running "flatpak update" was not great idea, but I did it anyway. I ended up with a KiCAD migrated to version 10, which deleted almost all of my settings and plugins, and FreeCAD also migrated to something new, which looks horrible. Maybe I shouldn't touch anything today…
2 weeks ago
Actions
👋 Join Station
9 Replies
❤️ lieselotte
It wasn't that painful, it was much more inconvenient. New version runs much smoother than previous one, which is great, it has a lot of new functionality. That plugin issue was caused by the fact, official KiCAD pages was unaccessible to me (Cloudflare vs czech O₂…this happens very often.) at the moment I started the new version for the first time. I definitely need to take much more care about WHAT is being updated to prevent this from happening in the future. The flatpak overhead probably is not that bad as new flatpak version of KiCAD runs much faster than native version 7.
I was just slightly unhappy with the whole situation at the first glance. · 1 week ago
☀️ skaffi
Do be aware that, as far as I know, Flatpak doesn't allow you to install two different versions of an app at the same time, as they wluld share the same namespace. You can work around that, however, by putting the flatpaks on removable media, and loading the app from that, or do essentially the same by putting each version whereever, and then mounting the one you need to the correct path for flatpak, or you coukd do something similar with symlinks, and changinf where they point to when you want to change. Sorry if I'm repeating stuff you already know, or thought of, btw! · 2 weeks ago
☀️ skaffi
The easiest way would be to see if the old version has been packaged by/for your distribution, and then install that. If you *need* it as a flatpak, then you can also compile and package it yourself. Flathub should link to a git repo with everything needed to package it yourself. · 2 weeks ago
☀️ skaffi
Yeah, flatpaks are also more of a last resort for me. Anyway, @lieselotte, I definitely feel your pain. If its more than just a nuisance, and it's genuinely debilitating, then you do have some options. You wikl be able to install the previous version, eitger instead of, or concurrently with the new version, even if the old version is no longer distributed by flathub. · 2 weeks ago
🌲 half_elf_monk
i use flatpak for a couple programs, but I'm never quite sure if it's worth it. three's more overhead resource use this way, and my old/recycled machine seems to complain. idk if I really need it. · 2 weeks ago
😹 userfxnet
Btw normally your settings shouldn’t clear or anything unless the rolled back install somehow saved to a folder which is overriding (as opposed to overwriting) the appropriate folder, you should be able to verify this is the case via checking ~/.var/app and looking for multiple instances of the packages you’re dealing with or maybe even checking within the familiar folders for any inconsistencies, duplicate files, etc · 2 weeks ago
😹 userfxnet
@lieselotte which is why I ask, iirc mint is meant to manage which branch of release you take updates from in order to ensure you keep within the release cycle appropriate to you. Did you check if your configurations for the branch those packages update from reflect the ones you need to make sure you’re at latest instead of being bogged back to a stable or rolled back cycle, or if this somehow changed? · 2 weeks ago
❤️ lieselotte
Mint, but it doesn't matter when it comes to Flatpaks. The thing is that migrating between major versions of software like KiCad or FreeCad needs to be treated differently to a regular update. It needs some time to settle and manage all consequences such a big upgrade causes. It's not simple intuitive software you learn in a minutes, furthermore, KiCad lacks downwards compatibility, so whole team have to be on the same major version which requires coordination. Imo there should be different flatpak for every major KiCad version. · 2 weeks ago
😹 userfxnet
oof. what distro? · 2 weeks ago