Steve Langasek wrote: > On Tue, Mar 28, 2006 at 03:29:27PM -0500, Michael Spang wrote: > > Why would you do this? The normal semantics of make *deliberately* allow > you to use the output of a previous make run; requiring clean before every > build excludes a valid use case, whereas the standard tools > (dpkg-buildpackage) account for the converse quite satisfactorily already. > > Cheers, I did so because it allows the .deb to be built flawlessly with a single "debian/rules" rather than dpkg-buildpackage which does several things unnecessary for either testing or building for installation rather than upload. The most annoying thing is the prompt for my gpg pass phrase unless it is run with two arguments. I have been using rules directly because of this annoyance. Rather than manually cleaning between tests, I added the dependency of build on clean that caused this bug. It was merely for convenience. Of course dpkg-buildpackage already ensures that the tree is clean. I found it quite irritating, however, to find the package installed over top of an older revision during testing. I added the dependency in response to this. Regardless, the new revision has already been uploaded thanks to Don Armstrong.
I will rework rules to be more dpkg-buildpackage friendly for the next release. Currently some unnecessary work is done (building twice) but this is easily fixed. This will of course require moving the clean dependency again, this time to a new default target that dpkg-buildpackage will not use. I should have done this in the first place, but I'll admit that I have been giving more consideration to my own way of doing things than the standard way. Michael Spang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
