Santiago Vila wrote:
> I see it as an inconsistent state which does not make any sense.
As far as I can tell, most people starting from the patches-unapplied
state keep that form in version control. If the build does not
involve modifying any source files (the usual case), they can use
usual commands like "vcs diff" and "vcs commit" when done --- that is,
dpkg-buildpackage returns the package to a normal state.
If dpkg left patches applied, we would get complaints that, after
running "debian/rules clean" by hand, the source tree is not clean and
ready to be committed.
Maybe people in this workflow would be happiest building with the -tc
option?
(Though as I said, personally I never start from the patches-unapplied
state, even when working on packages where that is the form kept in
version control. I prefer to keep things explicit:
QUILT_PATCHES=debian/patches quilt push -a
dpkg-buildpackage
debian/rules clean
QUILT_PATCHES=debian/patches quilt pop -a
vcs diff
Luckily that works fine.)
Hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
