On Tue, Dec 07, 2010 at 01:51:53PM -0400, Joey Hess wrote: > Roger Leigh wrote: > > It's basically down to the fact that "dh_auto_configure -i" and > > "dh_auto_configure -a" are treated separately so dh doesn't think > > it's been previously run (when it has been). > > So it happens eg when running debian/rules binary-indep binary-arch. > But that happens with unpatched dh too, and nothing calls both targets > when it can just call binary instead.
I think it's more likely to be triggered now, because you get this
type of thing (by default, unless you customise the rules):
debian/rules build
→ dh build
→ debian/rules build-arch
→ dh build-arch
→ debian/rules build-indep
→ dh build-indep
This will behave exactly the same as current dh, except for the fact
that dh_auto_configure will cause configure to run twice. Thinking
about it, dh_auto_build might possibly also trigger, but there the make
dependencies will ensure nothing happens (it's already done from the
first time).
This can also be triggered from a binary target:
debian/rules binary
→ dh binary
→ debian/rules binary-arch
→ dh binary-arch
→ debian/rules install-arch
→ dh install-arch
→ debian/rules build-arch
→ dh build-arch
→ debian/rules binary-indep
→ dh binary-indep
→ debian/rules install-indep
→ dh install-indep
→ debian/rules build-indep
→ dh build-indep
dpkg-buildpackage always calls the build target prior to any
binary targets, so the latter will never occur when a build
is done via dpkg-buildpackage (it will only recurse as far
as the install targets; well, it might go further, but it
won't actually /do/ anything because dh will record it as
already have being done).
Note that the debian/rules invocations are all printed out with
dh --no-act if you want to follow what's going on more closely.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
