I am part of various projects that develop open source software using the Rust language. I also used to be a Debian developer, but haven't been for many years. As upstream, my question is, what can I do to make it as easy as possible for Debian to package software written in Rust? I'm asking about this in general rather than for a specific project, though my question is triggered by the Radicle project. Based on my Debian experience, and my hazy understanding of how the Rust packaging team in Debian operates, here is my current thinking, but I would welcome advice. As upstream I can ensure that: * my code is published on crates.io * my code works with the Rust compiler and cargo in Debian unstable * my crate dependencies are packaged in Debian * my code works with the versions of crate dependencies that are packaged in Debian * I don't vendor any dependencies There are of course all the generic aspects of being packaged in Debian, but here I'm concerned about aspects relating to Rust specifically. To help myself estimate the packaging effort for my various Rust programs I wrote a little helper tool. It analyzes a Rust crate (or workspace) and its dependency graph, and makes a list of entirely missing crate dependencies, and a list of dependencies where the packaged version of a crate doesn't satisfy the version requirement of my program. The program is very quick and dirty: https://app.radicle.xyz/nodes/radicle.liw.fi/rad:z3PKKNstRjLYqhvGq9rxGy7LoEVr5 (I'd love it if someone wanted to take it over, and package it for Debian.) -- I want to build worthwhile things that might last. --joeyh
Attachment:
signature.asc
Description: PGP signature