pkglint suggestion: check pyproject.toml against pkgsrc-expressed dependencies
Greg Troxel <[email protected]> Sat, 09 May 2026 13:46:52 -0400
| Newsgroups | gmane.os.netbsd.devel.packages |
|---|---|
| Message-ID | <[email protected]> |
Recently I came across a py-foo where it depends on py-bar (does import) but where bar wasn't in the pyproject.toml. Also, I frequently find that pkgsrc (my packages anyway) are missing the expression of deps that are in pyproject.toml. I know url2pkg has some ability to examine pyproject.toml and create DEPENDS lines. It would be Really Cool if pkglint: parsed pyproject.toml and obtained dependency expressions for build tools, for runtime deps, and for test parsed Makefile for those TOOL_DEPENDS, DEPENDS, and TEST_DEPENDS. compared them, and created as output somehow the lines that are missing or replacements for those that are wrong This would ease updates by catching upstream bumps in versions, new deps, and no-longer-used deps. I have no idea how hard this is, but I'm not letting that keep me from suggesting it!