Hi,
On 03/02/2015 07:41 PM, Markus Koschany wrote:
I would like to know how other maintainers think about this issue and
wait until it is clear whether this issue will be fixed in Debian's
doxygen package or not. If it turns out that the project favors the
"patch-all-affected-packages" approach, then this patch can be quickly
applied. But I still have my doubts about the efficiency of this approach.
I talked to helmut as a doxygen maintainer on IRC and he pointed out the
following:
- dh_doxygen only runs after the build is completed and thus has no
way to influence the run of doxygen
- since it is impossible to determine the configuration file used by
doxygen during the build, the only working solution in practice
would be to move /usr/bin/doxygen to /usr/bin/doxygen.real and let
the former be a thin wrapper around the latter which detects using
environment variable when a package build is in progress and if so
determines the used configuration file and changes its value of
HTML_TIMESTAMP to NO before passing it on to doxygen.real
It is unlikely that such a fragile and hacky workaround will be included
in dh_doxygen.
Cheers, akira
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org