* Niels Thykier <nthyk...@moszumanska.debian.org>, 2016-07-31, 14:25:
+ m{
+ ^include \s+
+ /usr/share/(?:
+ dh-php/pkg-pecl\.mk
+ |pkg-kde-tool/qt-kde-team/\d+/debian-qt-kde\.mk
+ |blends-dev/rules
+ )
+ }xsm
+ ) {
+ # All of these indirectly use dh.
pkg-kde-tool/qt-kde-team/1 actually uses CDBS, but there are no users of
this version in the archive, so meh.
pkg-kde-tool/qt-kde-team/2 and /3 don't use dh. They use dhmk, which is
a different dh_* command sequencer with similar API. From the README:
dhmk is yet another debhelper command sequencer. Unlike dh(1), it uses
make(1) to execute all commands. The perl part (dhmk.pl) is used to
support dh(1) addons and dynamically calculate override_* targets.
dhmk aims to mimic the most useful features of dh(1) adding a couple of
its own. Some highlights include:
1) Unlike dh(1), dhmk sequencer is based on the traditional
debian/rules layout. It means that progress tracking revolves around
standard targets/actions (configure, build, install, binary etc.)
rather than on per-(command+package) basis (i.e. debian/*.debhelper.log
files) basis. "per-(command+package)" tracking gets complicated giving
not too much real benefit, but makes it hard to fix bugs like #510855.
2) Like dh(1), dhmk supports override_{dh_command} targets.
3) dhmk should support most of dh(1) addons.
4) Like dh(1), dhmk supports passing of additional options to all
dh_commands.
5) In addition to dh(1) addons, dhmk is extendable with makefile
snippets as well.
--
Jakub Wilk
