😬 I'd rather do "graceful degradation" of those features you touched if they weren't essential. I don't want to revert your PRs just because they break some old Qt version. In any case, you are the owner, so it's upto you. Native distro support is always the best integrated experience. Nobody should modify any content in this. You need to set the owner of that folder to Share. As you can see the owner is the root user and other users cannot access the files and folders inside it. I haven't seen ARM AppImages yet, but snap is supporting other archtectures and I'm not sure about flatpak. These are the permissions of the /media/pi folder. If anything isn't supported by AppImage, I would consider it very much dead given they go to great lengths to support old operating systems. I'm talking about ARM and other architectures. Note to self: We need some architecture stats.
#QOWNNOTES RASPBERRY PI 32 BIT#
What different branches in the config? And what config? The ini (and other) files?įor 32 bit x86, is that even a thing anymore? You will now have different branches in the config and other places for older Qt versions I very well know that you don't use Clion, I was just kidding you 😁
#QOWNNOTES RASPBERRY PI UPDATE#
I spend a huge amount of time to write update scripts for Windows and macOS to get around the manual process. The AppImage doesn't need to be updated, it can just be replaced. Ubuntu 14.04 (that we didn't even support officially because Qt < 5.3) has EOL April 2022! I don't think people using such old distros would even care or notice if QON stopped updating for them given they know they are living in a non-supported dead distro. Keeping a different branch would be even more work imho and we'd reconsider the whole OBS publishing because there need to be different sources to build from, so there would need to be different OBS projects with repositories. The rest of the code base can keep going forward and will not need to turn into a mess of #ifdefs and dirty workarounds all over the place.ĬLion by default hides all code paths that will not be executed on the local system.
like with the ssl library under Windows after a Qt update).Īnother suggestion, just branch out for older versions and backport any important fixes.
It would take a lot of effort to write an updater for the AppImage and those updater are always kind of brittle if anything isn't working (e.g. My main issue with the AppImage is that you can't update it easily. That's a completely dead distro since 5 years. I would be surprised if anyone else is writing or updating anything over there.
0 kommentar(er)
