<div dir="ltr">I don't think this is the right way to do it. The varnishapi package should depend on python.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 6:23 PM, Nils Goroll <span dir="ltr"><<a href="mailto:nils.goroll@uplex.de" target="_blank">nils.goroll@uplex.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
commit 49712a5fae5919e6e333d7164b98ef986b149c62<br>
Author: Nils Goroll <<a href="mailto:nils.goroll@uplex.de">nils.goroll@uplex.de</a>><br>
Date:   Thu May 21 19:21:28 2015 +0200<br>
<br>
    vmods running vmodtool require python, so check for it<br>
<br>
    (even if we exec env python, we should check early if we got one)<br>
<br>
diff --git a/varnish.m4 b/varnish.m4<br>
index 8339cb0..b7ad6f9 100644<br>
--- a/varnish.m4<br>
+++ b/varnish.m4<br>
@@ -81,6 +81,10 @@ AC_SUBST([VMOD_DIR])<br>
<br>
 AC_DEFUN([VARNISH_VMODTOOL],<br>
 [<br>
+AC_CHECK_PROGS(PYTHON, [python3 python3.1 python3.2 python2.7 python2.6 python2.5 python2 python], "no")<br>
+if test "x$PYTHON" = "xno"; then<br>
+  AC_MSG_ERROR([Python is needed to build, please install python.])<br>
+fi<br>
 VARNISH_PKG_GET_VAR([VMODTOOL], [vmodtool])<br>
 AC_SUBST([VMODTOOL])<br>
 ])<br>
<br>
_______________________________________________<br>
varnish-commit mailing list<br>
<a href="mailto:varnish-commit@varnish-cache.org">varnish-commit@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-commit" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-commit</a><br>
</blockquote></div><br></div>