[debhelper-devel] Bug#321825: Please warn/bail out if ran in wrong order

[Niels Thykier]

Control: tags -1 wontfix

On Sun, 7 Aug 2005 20:16:43 +0200 Jeroen van Wolffelaar
<jeroen at wolffelaar.nl> wrote:
> Package: debhelper
> Version: 4.2.32
> Severity: wishlist
> 
> I was just encountering a nasty bug in a package I was NMU'ing --
> dh_makeshlibs was run *after* dh_installdeb.
> 
> It'd be nice if debhelper would alert the user when ran in the wrong
> order. For example, it could store what dh_* scripts were already
> invoked in some subdir of debian (cleaned at dh_clean time), and alert
> when a script is being ran, while another script that depends on it has
> already be ran. It should surpress an error (and possibly only warn, or
> be silent at all) if it detects to be run itself for the second time, to
> allow for debugging sessions where people want to run things
> out-of-order.
> 
> Thanks,
> --Jeroen
> 
> [...]

Hi,

Thanks for the interest.

However, at this point, I think the dh sequencer have eliminated most of
these bugs.  The only method we have for tracking this, will almost
certainly end up creating false positives for manual
"retry-build-without-clean" builds (not entirely uncommon for debugging).

I think the best solution is to simply close this bug, recommending
people to use the dh-sequencer or cdbs over manually listing dh
commands.  This also have various other benefits like being able to add
new or retire old dh_commands easier.

Thanks,
~Niels