On Wed, Aug 09, 2023 at 04:16:29PM +0200, Jakub Ružička wrote: > * Package name : python-poetry-dynamic-versioning > Version : 0.25.0 > Upstream Contact: Matthew T. Kennerly <mtkenne...@gmail.com> > * URL : https://github.com/mtkennerly/poetry-dynamic-versioning > * License : Expat > Programming Lang: Python > Description : dynamic versioning plugin for Poetry > > This is a Python plugin for Poetry and Poetry Core to enable dynamic > versioning based on tags in your version control system, powered by Dunamai. > Many different version control systems are supported, including Git and > Mercurial. > > > Poetry is very popular in the Python world and this plugin makes it easy to > use dynamic versioning in Poetry-managed projects. > > Having this in Debian is a prerequisite for packaging of any projects using > poetry-dynamic-versioning. Some of existing packages require this in order to > update to latest upstream version which started using the plugin.
How will this sort of thing work when a git tree isn't necessarily available at binary package build time, since buildds build binary packages from a source package rather than directly from git and the source package doesn't usually include a git tree? Is it just a matter of causing the plugin to exist so that pybuild doesn't fail, but in practice the version is still going to be set by something that's actually in the source package? -- Colin Watson (he/him) [cjwat...@debian.org]
