[ZCM] [ZC] 1076/ 2 Reject "zopecrl and runzope scripts points to wrong python location"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1076 Update (Reject) "zopecrl and runzope scripts points to wrong python location"
 Status Rejected, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1076

==============================================================
= Reject - Entry #2 by mcdonc on Oct 23, 2003 4:49 pm

 Status: Pending => Rejected

I can't replicate this problem.  If you run "make install", the zopectl and runzope scripts will embed the name of the python interpreter found during "configure" (which is the thing that writes the makefile).

It is not reasonable to have a config file here because both of these scripts are "bootstrap" scripts.  These are the scripts that do indeed need to know a real path so the rest of the machinery doesn't.  Adding a configuration file would be overkill, IMHO.  I realize it's a matter of opinion, but that's mine. ;-)
________________________________________
= Request - Entry #1 by Anonymous User on Oct 6, 2003 9:57 pm

It seems that zopectrl and runzope scripts from current cvs checkout uses hard-coded python paths /usr/bin/python2.3

On my linux system python 2.3.2 installs to /usr/local/bin/python so Zope fails to start without modifications of those scripts. I think it is better to use python path provided to (or determined by) ./configure when making new zope instance.

Also, i propose to move PYTHON, ZOPE_HOME and other config params out of zopectl and runzope and place them to some config file so both scripts can use the same values

 
==============================================================