[Bro-Dev] #442: Hardcode Python path

[Bro Tracker]

#442: Hardcode Python path
-------------------------+--------------------
  Reporter:  robin       |      Owner:  jsiwek
      Type:  Problem     |     Status:  new
  Priority:  Normal      |  Milestone:  Bro1.6
 Component:  BroControl  |    Version:
Resolution:              |   Keywords:
-------------------------+--------------------

Comment (by jsiwek):

 > BroControl currently uses `#! /usr/bin/env` to find the Python binary at
 runtime. Craig suggested this instead:
 >
 > > I think the best way to go is to find python on the users path at the
 > > time bro is built and use that full path in all python scripts (e.g.
 at
 > > the point where the broctl.in template is transformed into broctl).
 >
 > Jon, is that something we can teach cmake to do?

 It's possible, but can you explain the underlying issue with `#!
 /usr/bin/env python` ?

 By using that in the shebang, the user selects which python they want by
 re-arranging their `PATH`.

 If an absolute path to a python interpreter is set in the shebang at
 configure/build time, then to change the python interpreter that is used,
 the user has to either (1) edit the script(s) or (2) re-
 configure/build/install `broctl`.  These seem like the more "difficult"
 options to me.

-- 
Ticket URL: <http://tracker.icir.org/bro/ticket/442#comment:1>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker