so! the phone update is going nicely! overnight it built 63 more packages, leaving 71 to go. for the last 45 minutes it has been building qtwebengine-6.9.0, which is needed by pyside6-6.9.0, which is needed by syncplay. it's tempting to just remove syncplay from the package list and see what that does... in fact, we think we're going to. it's really more of a desktop kind of task.

so we just spent a minute digging into why that was in there in the first place, and we realized there's a small tangle of files in our config repo that pull each other in in kind of a counterintuitive way. these were some of the first files we ever wrote for this config, upwards of ten years ago now, long before we had any low-resource devices using it. we definitely need to sort that out.

Show thread

for now, we commented out syncplay. we almost never use that, even on desktop - it's for watching videos with friends who aren't physically present

Show thread

it's been a few years since we've tried them, but we have the sense that the big-organization Linux phone setups each go hard on either only using qt, or only using gtk. do we have that right? has anyone reading along tried this in the last three years?

Show thread
Follow

@ireneista Depends what exactly you mean. When it comes to PureOS (not exactly a "big" org though 😜), we have only actively worked on GTK / GNOME / Phosh, but all the other stuff was still flowing in from Debian. We had set qtwayland up in the default config for Librem 5 to let Qt apps run well, but that was pretty much it. Ultimately it's just a matter of focus and resources, as we're all spreading ourselves thin and the community is still very tiny.

@dos that's good to know. your approach is the one we'd take in your shoes (those shoes being that you're closely associated with a corporate entity selling a hardware product), and it's compatible with eventually having a robust ecosystem, so we're glad.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml