Hello Jonas,
Am 25.01.25 um 17:46 schrieb Jonas Smedegaard:
Hi Carsten,
Quoting Carsten Schoenert (2025-01-25 15:42:45)
* Package name : python-minijinja
Version : 2.5.0
Upstream Contact: Armin Ronacher <armin.ronac...@active-4.com>
* URL : https://github.com/mitsuhiko/minijinja
MiniJinja is a single project upstream, where the core part is already
packaged in Debian as source package src:rust-minijinja.
I find it more sensible to extend the existing Debian source package
than tracking same source multiple times and packaging it spread across
multiple source packages.
sure, but the existing package is using the same way as I decided to
take. They use only the folder with the Rust source.
https://sources.debian.org/src/rust-minijinja/2.5.0-1
The src/ folder is taken from
https://github.com/mitsuhiko/minijinja/tree/main/minijinja
while I wrote a postunpack hook to use the files/folders from
https://github.com/mitsuhiko/minijinja/tree/main/minijinja-py
But I've no clue how the Rust team has created the src package
structure, there is now READAME.source in the debian/ folder which I
typically use for such hints and information.
If the Rust team would also import the folder with the Python sources
then it would of course be possible to just extend the build about the
Python library.
I've stopped writing wishlist bugs against Rust packages as I almost
never have got any answer.
I can offer to co-maintain such larger package, or if you and/or the
existing maintainers of rust-minijinja for some reason prefer not to
collaborate with me then I can suggest that you consider using the
helper tool dh-rust, since dh-cargo by design handles only a single
cargo crate at a time so is cumbersome to use with multi-crate
workspaces.
If you haven't seen or realized it, I'm talking about the Python library
and we use dh-python not surprisingly, but you know this for sure.
The Python library doesn't need to handle and use any dh-cargo or
dh-rust stuff.
Of course it would be nice if we would not need to split of into
multiply src packages for this and similar packages. OTOH I think for
python-minijinja it's also not that complicated as the Python package is
only depending while building on the correct version of the Rust dev
files. The usage of the library hasn't any external requirements beside
Python3 of course.
For now I wont wait for any movement in the package src:rust-minijinja.
That means not that at a later time the two source packages can get melt
together.
I have just low expectations it will happen.
--
Regrads
Carsten
