Re: Rust packaging approaches workship, Debconf in Brest
On Mon, Mar 31, 2025, at 7:21 PM, Ian Jackson wrote:
> Hi.
>
> I would like to meet with other people involved in Rust packaging for
> Debian, at Debconf in Brest.
>
> I think there is considerable room for improvement in our workflows
> and the conference is an opportunity to understand the constraints and
> consider our options, outside of the usual day-to-day of packaging.
>
> I've both used the Rust Team tooling, and worked with Jonas's dh-rust,
> which means I feel I have some perspective. Ideally I'd like to get
> together and have a session involving vigorous handwaving and/or
> scrawls on available pieces of paper.
>
> Specific areas where I think we have opportunities for improvement
> include:
> - version dependency handling (automating and removing clerical work)
> - git-native approaches (ie, packaging based on upstream git)
> - workspace-per-a-source-package
> - abolishing feature virtual packages
> - within-Debian-archive metadata management
>
> I don't think we need to come to complete agreement; we already have
> two approaches that coexist relatively well. I'm hoping that we can
> try to converge somewhat.
Yes, I don't think all of the above will be points where we can settle
on a single approach/solution/opinion, but I also think some more
coordination and exchange would not hurt.
> So:
>
> I'm considering submitting a workshop proposal for Debconf 25. If you
> think this sounds interesting, please LMK (and in particular if you
> have any time constraints, opinions, etc).
>
> NB this will not be a Rust Team meetup. One of those may well be a
> good idea, too. I don't feel sufficiently embedded in the Rust Team
> to take the lead on organising that.
I would join such a workshop or BoF. I plan on being in Brest from
Monday afternoon until Sunday (for DebConf, sadly won't make DebCamp).
I have considered submitting a "Rust Packaging 101" talk (from the
team and toolchain packaging perspective, I don't maintain any packages
using dh-rust or upstream git as opposed to crates.io as orig tarball
source), since it seems to be a recurring question why things are done
as they are. Obviously some of that applies to all Rust packaging (such
as the fact that we have to statically link), not just debcargo/dh-cargo
based packages. Nothing settled in stone yet though, maybe I'll submit
something different (State of the Rust Toolchain in Debian, something
virtualization or derivative related, or something completely different).
Thanks for getting the ball rolling!
Fabian
Reply to: