Am 25.03.2017 um 08:58 schrieb Niels Thykier: > Michael Biebl: >> Am 24.03.2017 um 06:53 schrieb Michael Biebl:
>> Related to that: For a source tree which ships both meson.build files >> and configure.ac, autoreconf is run, even if I explicitly choose meson >> via dh $@ --buildsystem=meson >> >> Niels, is there a way how I can skip the dh-autoreconf step(s) if meson >> is used? >> >> Michael >> > > That would be #842246. The easiest thing is probably just overriding > command. Hm, I see, so apparently/obviously other build systems are affected by this as well. By overriding, do you mean, that package maintainers have to that manually via %: dh --without autoreconf Or did you mean something else? Ideally dh_update_autotools_config and dh_autoreconf are only run if the active build system is autotools. Is it possible to change dh to only add the autoreconf sequence depending on whether autotools is the active build system (not just autodetected). Or is it possible to decide this from within the dh_update_autotools_config and dh_autoreconf helpers so they are always run but become a nop if buildsystem != autotools ? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature