Hi Peter,
I believe the previous way of doing this was -
override_dh_foo:
dh_foo
<do stuff>
which is now less verbose if you want -
execute_after_dh_foo:
<do stuff>
or execute_before, when you need that.
My understanding is that there is no added benefit than less verbosity and
maybe more clarity (since it tells you in a first glance that it should run
before/after dh_foo). So yes, nothing problematic as long as you still have
dh_foo there once you use override_dh_foo, but these execute_* targets feel
much better to me. tbph, overriding a target only to run the exact same thing
again makes me feel stupid each time, so I change the older patters whenever I
come across them in a package :p
Best,
Ananthu
On 8 December 2024 5:36:32 pm UTC, Peter Wienemann <wi...@debian.org> wrote:
>As long as the override_dh_auto_clean target still contains dh_auto_clean the
>original functionality should be retained. At least this is my understanding.
>Please correct me if this is wrong. But you are perfectly right that using
>execute_after_dh_auto_clean is less error-prone. Thanks for this suggestion. I
>added it to my notes. :-)
>
>Best regards
>
>Peter
