On Sun, May 29, 2011 at 02:15:08PM +0200, Reinhard Tartler wrote: > In source format 3.0, the option 'unapply-patches' (usually set in > debian/source/local-options) is used to indicate that patches are to be > unapplied after building the package. This is commongly used when the > package itself is maintained in a VCS that contains unpatched upstream > source and where you want to keep the tree unpatched even after a > package build. > > Having 'debuild clean' and 'debclean' respecting this setting would > streamline the workflow with source format 1.0, where a 'debclean' > restores the source tree to a state that allows further VCS operations > such as investigating and committing changes easily.
Adding 'dpkg-source --after-build'/'dpkg-source --before-build' calls to the dpkg-buildpackage emulation of debuild does make sense and I'll add that. Honoring unapply-patches from 'debuild clean' doesn't correspond to how debuild is intended to work when the standard targets are given. In that case, it's just a thin wrapper around 'debian/rules <target>'. This is also how 'dpkg-buildpackage --target <target>' works. I'm also hesitant to add this behavior to debclean by default. Adding an option to call 'dpkg-source --after-build' is a possibility, but doing it by default so that there's parity with 1.0 source packages isn't a good enough argument. 1.0 source package and 3.0 source packages are handled differently by dpkg's tools and the devscripts tools should follow their lead in that regard. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org>
signature.asc
Description: Digital signature
