Post #2919542

2026-04-23 15:17 UTC

@red@woof.tech I'm afraid this communication doesn't answer the question, "why fork?" Why not simply use Debian + custom repo (or even just Sid/Testing repos), to ensure we're benefiting directly from Debian's time-proven infrastructure and processes? Debian users already have flatpak and appimages for cutting edge, but it would be better to incorporate ham software quickly into Debian while complying with Debian review and security processes. So give it another try: "Why fork?" What's the benefit?

Replies (1)

@red@woof.tech 2026-04-23 15:24

@fossham@mastodon.radio I don’t see me forking - can you highlight what bit I forked? You’re describing to me what I have done. I am using Debian stable repo, Debian backports repo and 1 custom repo containing a few packages. They are used to build the image and if you cat the apt sources list, they’re Debian. We’re benefitting from Debian’s time proven infrastructure and processes because that is where the packages come from, and 95% of my work on this is upstreamed by me being on the team. You can check my ddpo & Debian portfolio if you need to see my packages, backports, sponsors and the like to see what I’m doing upstream already. No one else on the hams team wants to generate, test and maintain it so I’m not doing it under the banner of the team or the distribution or hosting a download link at Debian.org or debian.net.

Open ##2919543