Post #3276465

2026-04-30 08:19 UTC

@vwbusguy@mastodon.online @bookwar@floss.social @tragivictoria@mastodon.catgirl.cloud Only if: upstream distributes itself for all relevant architectures (especially RISC-V tends to be problematic and the Ubuntu packages are saving my ass often) upstream backports security fixes, so users don't have to do breaking updates upstream provides timely updates when there is a security issue in any library the package includes I usually prefer upstream provided Snap, AppImage, or Flatpak packages myself too, but I don't think it's viable for all types of software, so some form of distributing will always happen.

Replies (1)

@tragivictoria@mastodon.catgirl.cloud 2026-04-30 08:45

@jcm @vwbusguy@mastodon.online @bookwar@floss.social upstream distributes itself for all relevant architectures (especially RISC-V tends to be problematic and the Ubuntu packages are saving my ass often) How about contributing support for these architectures upstream? so everyone can make use of them upstream backports security fixes, so users don't have to do breaking updates Admittedly I don't entirely understand this point. I assume you mean this for projects that support multiple releases? Why not contribute these backports upstream, then? upstream provides timely updates when there is a security issue in any library the package includes if upstream is failing at this, forking may be a good solution

Open ##3276466