Re: [PATCH 2/2] python-pkg: Fix lirc version detection when cross compiling

[Alec L. <lea...@gm...>]

On 31/08/17 00:21, Michael Markstaller via LIRC-list wrote:
> 
> My thoughts - as cuurently fiddling with getting the ancient
> OpenWRT/LEDE package from 0.8x to a current release:
> 
> Couldn't it be a --disable-python switch ?
> 
> Reads like
> "I-dont-have-any-python-anywhere-here-and-never-wanted-or-needed-it" (to
> be involved in any part of the build-process of a C-program) ?
> 
> It surely makes sense to have python in the client API built etc. but
> why should python - at all - be a build-requirement for lircd itself ?

As of now, python is used in the build as a platform-agnostic tool. 
Overall, I'm less concerned about a python (really python3)  build 
dependency, especially when cross-compiling. I can't really understand 
that this BR should be a problem - python is really ubiquitous these 
days, and running python is much less demanding than compiling lirc.

As a runtime-dependency I'm open. It's sort of an uncommon testcase, but 
in general accepting patches to handle systems without python3 in the 
target host should be fine.


Cheers!

--alec