BIND 10 #158: run_bind10.sh does not really work

BIND 10 Development do-not-reply at isc.org
Wed Apr 21 19:39:22 UTC 2010


#158: run_bind10.sh does not really work
--------------------------+-------------------------------------------------
 Reporter:  jreed         |        Owner:  jreed   
     Type:  defect        |       Status:  assigned
 Priority:  major         |    Milestone:          
Component:  Unclassified  |   Resolution:          
 Keywords:                |    Sensitive:  0       
--------------------------+-------------------------------------------------
Changes (by jinmei):

  * owner:  => jreed
  * status:  new => assigned


Comment:

 Replying to [ticket:158 jreed]:
 > I don't see where in bind10 it knows how to run the run_*.sh components.
 >
 > So if no "make install" then b10-xfrin and b10-xfrout can't find
 bind10_dns and bind10_xfr (respectively) for example.
 >
 > I had worked at making the run_*.sh scripts be able to find libraries in
 the source tree, so they do work if ran individually.

 We can pass PYTHONPATH from the boss as an environment variable.

 One possible problem is that the python scripts running in the "source
 mode" still refer to the installed paths, which may be confused (e.g. a
 script may use an installed, old version of library in some case and use a
 new version only in the source tree in the other case).

 I believe all of the problem is solvable by a patch like the one attached.

 And, I still believe it's beneficial to allow the programs to run under
 the source tree.  It will reduce the steps of code-build-try-fix by
 eliminating the need of 'make install'.

 If this is convincing, I'll apply the same fix to other scripts.

-- 
Ticket URL: <https://bind10.isc.org/ticket/158#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list