Modestas Vainius wrote:
> Since options to debhelper commands can be passed via DH_INTERNAL_OPTIONS,
> DH_OPTIONS and command line, the first two are typically not visible in the
> logs. Invisibility of DH_INTERNAL_OPTIONS is especially bad since dh puts
> "black magic" in there. To better expose this, dh should print a final command
> line of dh_* commands as they are executed.

I don't think that DH_OPTIONS is a problem since the maintainer
determines it themselves.
 
> My previous patch proposed dh_* to print their command line by themselves. 
> Now 
> I attach a proof of concept implementation (sequencer, aka dh, and 
> dh_command) 

Wow, that's so complicated!

I was thinking about this problem today in the context of #541773,
and it came to me that all debhelper need was an -O option that
dh could use to pass user-supplied options to each command it runs. This
is a kind of optional option; if -O--foo is passed and a command does
not know about --foo, it just ignores it.

Result is:

    dh build -B build --parallel 2 --foo="bar baz"
dh_auto_test -O-Bbuild -O--parallel=2 "-O--foo=bar baz"
dh_auto_build -O-Bbuild -O--parallel=2 "-O--foo=bar baz"

DH_INTERNAL_OPTIONS is still hidden. It might make sense to say:

make -f debian/rules override_dh_auto_build DH_INTERNAL_OPTIONS=-O-Bbuild...

But, since DH_INTERNAL_OPTIONS currently uses non-printable separator
characters, that's a small problem. Also, if the variable were exposed
this way it should probably be renamed.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to