Bug#499225: [PATCH 1/2] Support waf (closes: #499225).

2009-02-24 Thread Trent W. Buck
--- dh_auto_build |5 - dh_auto_clean |5 - dh_auto_configure |5 - dh_auto_install |5 - dh_auto_test |3 +++ 5 files changed, 19 insertions(+), 4 deletions(-) diff --git a/dh_auto_build b/dh_auto_build index a3c9521..92c3a78 100755 ---

Bug#499225: [PATCH 1/2] Support waf (closes: #499225).

2009-02-24 Thread Joey Hess
A few questions: * Earlier, you said you wanted to run waf in preference to configure, but this looks to run it after? * Is there any good reason to add the check for waf before the check for Build.PL? While it seems unlikely a package would include both, this could in theory change how

Bug#499225: [PATCH 1/2] Support waf (closes: #499225).

2009-02-24 Thread Trent W. Buck
On Tue, Feb 24, 2009 at 11:18:51PM -0500, Joey Hess wrote: A few questions: * Earlier, you said you wanted to run waf in preference to configure, but this looks to run it after? That was based on the existing behaviour for Make.PL and setup.py, which both defer to autoconf should it exist.

Bug#499225: [PATCH 1/2] Support waf (closes: #499225).

2009-02-24 Thread Joey Hess
Trent W. Buck wrote: I stuck it directly below setup.py because they're both python thingies. I'm not really fussed if you would prefer it to go below. I think it's safest to always add new stuff the the end of these commands. Of course, that might mean the wrong stuff runs in some weird