Bug#959533: dh: List addons in sequence

[Christian Kastner]

On 2020-05-03 14:04, Niels Thykier wrote:
> Hi,
> 
> Are you using
> 
>   dh binary --no-act
> 
> with debian/rules containing:
> 
>   dh $@ --with=python3,sphinxdoc
> 
> ?
> 
> In that case, you are comparing apples with oranges.  You would have to use
> 
>   dh binary --no-act --with=python3,sphinxdoc
> 
> To see the sequence with the add-ons applied (or use the "new-style"
> Build-Depends on dh-sequence-python3, dh-sequence-sphinxdoc).

While my initial report indeed makes it look as if I were mixing the
two, I was actually correctly using the latter.

My mistake was in expecting a sequence element which is not needed for a
particular target (in my case, build-*).

I only realized this when I progressed to the next issue in my testing.

Bug#959533: dh: List addons in sequence

[Niels Thykier]

Control: tags -1 moreinfo

On Sun, 3 May 2020 13:57:45 +0200 Christian Kastner  wrote:
> Package: debhelper
> Version: 13
> Severity: wishlist
> 
> Whiles debugging an issue with a build sequence, I noticed that
> 
>   dh  --no-act
> 
> does not list where the addons come into effect. Specifically, I have a
> package that uses
> 
>   --with=python3,sphinxdoc
> 
> but it's not evident where in the sequence the addons will be called to
> do their magic.
> 
> Or (as is in my specific case) if they will be called at all: it's
> conceivable that dh_sphinxdoc get's only called in indep targets, for
> example).
> 
> It would be appreciated if the addons' activities were also listed in
> the sequence.
> 
> 

Hi,

Are you using

dh binary --no-act

with debian/rules containing:

dh $@ --with=python3,sphinxdoc

?

In that case, you are comparing apples with oranges.  You would have to use

dh binary --no-act --with=python3,sphinxdoc

To see the sequence with the add-ons applied (or use the "new-style"
Build-Depends on dh-sequence-python3, dh-sequence-sphinxdoc).

~Niels

Bug#959533: dh: List addons in sequence

[Christian Kastner]

Package: debhelper
Version: 13
Severity: wishlist

Whiles debugging an issue with a build sequence, I noticed that

  dh  --no-act

does not list where the addons come into effect. Specifically, I have a
package that uses

  --with=python3,sphinxdoc

but it's not evident where in the sequence the addons will be called to
do their magic.

Or (as is in my specific case) if they will be called at all: it's
conceivable that dh_sphinxdoc get's only called in indep targets, for
example).

It would be appreciated if the addons' activities were also listed in
the sequence.