One other thought. One of the reasons I have a *strong* opinion why
patches-applied is the superior way is because I want to be able to
run native build and regression tests --- e.g., "./configure ; make ;
make check" on the git repo should run the tests on the same codebase
as "dpkg-buildpackage -us -uc -b" --- the only difference that being
the config options specified by debian/rules might be different.
So my general pattern is to run a successive set of tests on the same
branch:
1) running "make check" in my development environment
2) running "dpkg-buildpackage" in my development environment
3) running "schroot -c sid -- dpkg-buildpackage" to test whether
things work in a non-hermetic unstable environment
4) running "gbp buildpackage" which runs a package build in a hermetic
environment
... and only *then* will I start the dgit workflow.
This might waste some CPU, but if there is a change in the unstable
version of pkgconfig[1], that might be a reason why (2) passes, but
(3) does not. And CPU time is much cheaper and more abundant than my
personal time.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126636
And most *definitely* I want to be able to test and debug things
locally before I try to use tag2upload.
- Ted
