Re: dpkg-buildpackage vs sbuild with python packaging
On Jun 11, 2025 17:57, PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> wrote:
>
> > This is a sitation where upstream tarballs are preferable to git.
>
> Yes but for now the package is only distributed via git...
>
> Even worse, it is use via a checkout and that's all.
>
> > If you use an sdist, the egg-info / dist-info in the sdist will contain
> > a file list that setuptools-scm can use.
>
> Maybe I can generate this sdist via uscan. It would solve my problem.
>
> Fred
Don't do that. Just add a MANIFEST.in and write in it:
recusive-include <folder-name> *
(Something like that...)
and setuptools will likely package all data files. I did that in MANY OpenStack packages. I can find one example if you need one.
As for the version, setuptools-scm understand an env var that you may set with something like:
export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog -something)
(Again, top of my head, look it up on other packages to get it right, and you can ask me again if you cant find it yourself...)
Then both your issues will be fixed.
Hoping this helps,
Cheers,
Thomas Goirand (zigo)
Reply to: