Bug#1052404: RFP: axum -- web application framework that focuses on ergonomics and modularity

[Alexander Kjäll <alexander.kjall@gmail.com>]

I think the solution here is to mark some of the autopkgtests as
broken. The dependency loop is only there if you take dev-dependencies
into account and those are mostly optional to package. I can make an
attempt on packaging them.

//Alex

Den tors 21 sep. 2023 kl 13:03 skrev Reinhard Tartler <siretart@tauware.de>:
>
> Package: wnpp
> Severity: wishlist
>
> * Package name    : axum
>   Version         : 0.8.0
> * URL or Web page : https://github.com/tokio-rs/axum
> * License         : MIT
>   Description     : web application framework that focuses on ergonomics and modularity
>
> Hey folks, I need help packaging axum.
>
> This package is a new dependency of https://github.com/hyperium/tonic,
> which is needed by newer versions of netavark (which is the userspace
> network stack for podman, the alternative to docker)
>
> I struggle with packaging this package because it consists of two crates
> that depend on each other. Upstream uses a workspace build and publishes
> all of them, that is, axum, axum-core and axum-macros at the same time.
> Turns out that the debcargo-conf infrastructure is not suitable for
> this.
>
> Can someone please give me a hand with packaging these three crates so
> that they are built from a single debian source package?
>
> Thanks!
>