Roger Leigh wrote: > +If running a configure script, it may be necessary to prevent it being > +run twice, once for architecture-independent packages, and again for > +architecture-dependent packages. This may be accomplished by > +overriding L<dh_autoconfigure(1)>: > + > + override_dh_auto_configure: config.status > + > + config.status: > + dh_auto_configure -- $configure_options
Is this patch somehow making it more likely that configure scripts run by override tagets will be run twice? In my testing they run twice when running debian/rules binary-indep; debian/rules binary-arch, but so too without the patch. > +A sequence can also run dependent targets in debian/rules. For > +example, the "binary" sequence runs the "install" target. This will > +show up in the dh output as "debian/rules install", but internally > +will be called "rules:install" in the sequence. The "install" > +sequence likewise runs "debian/rules build", internally named > +"rules:build". The dh man page does not need to document implementation details. -- see shy jo
signature.asc
Description: Digital signature
