[ZCM] [ZC] 1320/ 2 Comment "runzope.bat silly"

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

Issue #1320 Update (Comment) "runzope.bat silly"
 Status Pending, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/1320

==============================================================
= Comment - Entry #2 by chrisw on May 7, 2004 8:17 am

In fact, the 1st 2 line should also be:

@set ZOPE_HOME=e:\Zope\2.7.0
@set PYTHON=%ZOPE_HOME%\bin\python.exe
________________________________________
= Request - Entry #1 by chrisw on May 7, 2004 7:31 am

The runzope.bat generated by the Win32 installer is sub-optimal:

@set PYTHON=e:\Zope\2.7.0\bin\python.exe
@set ZOPE_HOME=e:\Zope\2.7.0
@set INSTANCE_HOME=E:\Zope\2.7I
@set SOFTWARE_HOME=e:\Zope\2.7.0\lib\python
@set CONFIG_FILE=E:\Zope\2.7I\etc\zope.conf
@set PYTHONPATH=%SOFTWARE_HOME%
@set ZOPE_RUN=%SOFTWARE_HOME%\Zope\Startup\run.py

two lines should really be as follows:

@set SOFTWARE_HOME=%ZOPE_HOME%\lib\python
@set CONFIG_FILE=%INSTANCE_HOME%\etc\zope.conf

...that way you don't trip yourself up by copying an instance home and only changing one of the lines, resulting in you starting up Zope inadvertantly using he worng zope.conf and so packing the wrong ZODB ;-)

As a side issue, it feels wrong to me to have to specify INSTANCE_HOME and SOFTWARE_HOME in both the start script AND zope.conf. Why is it necessary?
==============================================================