Sebastian Krzyszkowiak @dos@librem.one

@martijnbraam Though depending on application you'll also want to be quite cautious about track routing. My prototype suffered from ghost touches cause it turned out the tracks were where your finger tends to rest while holding the board for longer 😂

@martijnbraam Give them some proper clearance from that ground plane and don't fill the ground on layers underneath (or use partial fill if it's necessary). Otherwise it's pretty simple indeed 😜

@jplebreton @mcc A-Frame is from 2015.

@raptor85 @sos @gamingonlinux Ever since Deck was released I suspected that Valve will eventually want to migrate away from Arch as a base for SteamOS because of some of its properties simply making it a less-than-ideal choice for such project long term. However, it looks like they decided to throw money at Arch to have them provide the things they're going to need instead. I haven't thought about that possibility, but in hindsight it is a totally Valve move 😂

@craftyguy IMO the worst thing about Debian packaging is that the answer to your question is: It Depends™. Every maintainer is free to do things their own way.

If you're lucky and the package in question follows DEP-14, you'll most likely easily get there with gbp: https://wiki.debian.org/PackagingWithGit

If you're unlucky, you'll need to possess enough understanding of everything to react to what you stumble upon there. Which isn't rocket science, but isn't beginner-friendly either - RTFM required 😉

@sos @raptor85 @gamingonlinux Mind you, I don't think Valve cares about FLOSS at all. It just happens to be the best available path for them, especially since they don't seem to care about locking things down either. In the end, everything they do is there to support Steam, one way or another.

@sos @raptor85 @gamingonlinux Yeah, as we all know, withholding the source magically provides your project with more devs and gives them wings to do more in less time ;P

The opposite is true in fact. It wouldn't be possible to create a product like Deck with such a small dev team without relying on synergies with already well-established projects and communities. Their choices are pretty smart in this regard.

And that's just pure pragmatism. They have strategic reasons to do it this way too.

@sos @raptor85 @gamingonlinux And that would help them how? :p

@raptor85 @sos @gamingonlinux That description applies to Gentoo, but doesn't to Arch. Even Debian would be better than Arch in this regard - just look at SteamOS's post-install rootfs cleanup that's done behind pacman's back. They didn't "build their own distro" at all, they just roll with repo snapshots and overlays (which is perfectly fine, as that's exactly what they needed there).

@sos @gamingonlinux Why would they? That would only make the whole project significantly more complex and expensive without providing tangible benefits.

What's harder to understand, especially with this news above, is why they went with Arch specifically - although ultimately the choice of base distro isn't that important with their atomupd design.

@linmob @tbernard ...or even N900 in the decade before L5 😂

@mort @Doomed_Daniel You'd still have to switch it away from your default printer manually.

@gbryant Betteridge's law of headlines 😂

@williamtries There are other issues, some quite annoying, sure, but I haven't had any troubles with calls and call audio on my Librem 5 with PureOS for years now, so I don't think it's as hard as you make it seem. Unless you reach for bleeding edge (I don't see PipeWire stacks as ready for mobile just yet), this is a solved problem; and when you do, there are still some low hanging fruits to reach for in order to solve it.