Post #796338

2026-03-11 13:03 UTC

For our #Rust projects, we created a bespoke #OpenSource pipeline to build and publish binary packages for the last three major versions of Debian, Ubuntu, RHEL and derivatives. Ploutos is now almost four years old, and the way #rustlang packaging is done for these OSes has evolved quite a bit. The pipeline is also closely built around GitHub Actions, and now that we&#39;re moving to @Codeberg we need to overhaul it anyway. Any tips or experiences from the Rust community? https://github.com/NLnetLabs/ploutos

Replies (4)

@pauldoo@mastodon.scot 2026-03-11 13:11

@nlnetlabs @Codeberg devil’s advocate, but do you need distro native packages? Can you publish instead in a distro agnostic form? Maybe an OCI image, flatpak, or Brew package..

Open ##1304361
@mxfraud@tabletop.social 2026-03-11 13:20

@nlnetlabs I use goreleaser in my forgejo pipeline to build different artifact (binaries, .deb). I find it useful because it supports multiple languages, multiple archs, and multiple packages type. The main website is at https://goreleaser.com /cc @Codeberg@social.anoxinon.de

Open ##1304367
@misty@digipres.club 2026-03-11 17:08

@nlnetlabs I’ve been thinking about Codeberg pipelines for the cargo-dist release management tool - right now it’s also tied very closely to Actions, but I’d prefer that it not be. Have you started looking into the details, or are you early in considering it? I did see that they recently shipped a major new feature that closes one of the remaining feature gaps between the systems, which should make it easier to switch.

Open ##1304368
@unsafe@m.webtoo.ls 2026-03-12 06:10

@nlnetlabs @Codeberg this strikes me as the „Cargo not being enough build system“ problem… There were ideas of a cargo-aware build system but none that panned out in practice unfortunately i’ve been looking at buck2 recently and I think it’s a good fit for k23 and our some of our work projects, but its a big commitment

Open ##1304375