Hello Matheus, Am 15.06.26 um 04:11 schrieb Matheus Polkorny:
I tried keeping both packages under the same source package, but the upstream monorepo is not directly buildable in Debian as-is. The workspace members rely on uv-dynamic-versioning for version generation, which is not currently packaged in Debian. As a result, building the monorepo requires either packaging uv-dynamic-versioning first or carrying a Debian-specific patch to replace the dynamic versioning with a static version. On the other hand, the standalone httpcore2 source distribution already includes the generated metadata required by hatchling and builds cleanly with pybuild without any additional patches. For that reason, I would prefer to keep httpcore2 as a separate source package rather than carrying a versioning patch that would need to be reviewed and updated for every upstream release.
You package isn't the first package that fall into this limitation and wont be the last. :-)
Patching out some uv/setuptools/PDM dynamic version tracking and replacing isn't taking very much effort. I've done this in some of the packages I did introduce into Debian in the past. It's mostly adjusting the patch queue on version bumping or doing some shell or Makefile magic in d/rules to work around in a more generic and general way.
By my experience it's always the better way to not build another source package and keep as much possible into one source package in case like this package, the two build library are connected together very closely.
I can have a look at your preparations once I've take a deeper look into. Mind to give me a link to your current WIP?
-- Regrads Carsten
