Hi
As long as the Rust crates are published on crates.io then I think it would be easiest to package them in the rust team :)
Hi Rust & Python teams,
I would like to package:
https://github.com/trailofbits/rfc3161-client
It is a Python library that ships with and needs a Rust crate to work,
the separation is best explained by upstream:
It is composed of three subprojects:
🦀 tsp-asn1: A Rust crate using rust-asn1 to create the types used by
the Time-Stamp protocol. This crate depends on rust-asn1 and
cryptography to minimize the amount of duplicated code. While it is
usable as a standalone crate, this is not officially supported. Drop
us a message if you are interested in using it.
🦀 rfc3161-client: Another Rust crate that provides Python bindings
to the tsp-asn1 crate using PyO3.
🐍 rfc3161-client A Python library using the crate above to provide a
usable API to create Timestamp Request and read Timestamp Response.
Are there similar projects that are packaged in Debian that I look at
for inspiration?
Any thoughts on if this be split up into two separate Debian source
packages, one maintained by the rust team following their policies and
ship the crates - and one source package maintained by the python team
following their policies that ship the library and depend on the rust
packages -- or just one source package with a more complicated
maintainership and build process?
I have started python-like packaging here:
https://salsa.debian.org/python-team/packages/python-rfc3161-client/
However it lacks the Rust part. Would someone who knows Rust want to
join me working on this package? I'm still learning Python packaging so
I hope to help on that, but I haven't done any Rust packaging at all...
forks, merge requests, commits etc appreciated.
/Simon