Jelmer Vernooij:
> Package: debhelper
> Version: 13.3.4
> Severity: wishlist
>
> For lintian-brush, it would be great if there was a command that printed the
> buildsystem that debhelper would use in a directory.
>
> At the moment, lintian-brush runs something like:
>
> perl -w -MDebian::Debhelper::Dh_Lib -MDebian::Debhelper::Dh_Buildsystems -e
> <<EOF
> Debian::Debhelper::Dh_Lib::init();
> my $b=Debian::Debhelper::Dh_Buildsystems::load_buildsystem(undef,
> %(step)s);\
> if (defined($b)) { print($b->NAME); } else { print("_undefined_"); }\
> EOF
>
> to do something like this.
>
> But it tends to trigger unnecessary perl warnings, and I'm worried that it'll
> break at some point as this is not a public API.
>
> [...]
Thanks for the suggestion, I will consider it for bookworm.
For now, I recommend you remove the call to init (you can also remove
the module import for Dh_lib as a side-effect).
Calling init makes debhelper think you are implementing a debhelper tool
and can cause your one-liner to create debhelper log files (especially
in older compat levels) as a part of its END handler.
Alternatively, if you do need to call init, then please at least pass
"inhibit_log => 1" to it or call inhabit_log prior to the init call.
Thanks,
~Niels
