Just dropping that at <<ZOPE_HOME>>\skel\bin
should do the trick, but it seems that mkzeoinstance.py does not use skeletons!
I guess it would be a bit awkward to have runzeo.bat
created by mkzopeinstance.py instead of mkzeoinstance.
I don't know if is there any interest in converting mkzeoinstance.py to use skeletons
(instead of code embeeded templates) ?
Nevertheless, I believe runzeo.bat would be a plus.
Since mkzopeinstance.py generates a nice runzope.bat,
but mkzeoinstance.py lacks a runzeo.bat,
I made a little runzeo.bat.in:
<runzeo.bat.in>
@set PYTHON=<<PYTHON>> <<ZOPE_ HOME>> HOME=<< INSTANCE_ HOME>> HOME=<< SOFTWARE_ HOME>> FILE=<< INSTANCE_ HOME>>\ etc\zeo. conf %SOFTWARE_ HOME% %SOFTWARE_ HOME%\ZEO\ runzeo. py
@set ZOPE_HOME=
@set INSTANCE_
@set SOFTWARE_
@set CONFIG_
@set PYTHONPATH=
@set ZEO_RUN=
"%PYTHON%" "%ZOPE_RUN%" -C "%CONFIG_FILE%" %1 %2 %3 %4 %5 %6 %7
</runzeo.bat.in>
Just dropping that at <<ZOPE_ HOME>>\ skel\bin
should do the trick, but it seems that mkzeoinstance.py does not use skeletons!
I guess it would be a bit awkward to have runzeo.bat
created by mkzopeinstance.py instead of mkzeoinstance.
I don't know if is there any interest in converting mkzeoinstance.py to use skeletons
(instead of code embeeded templates) ?
Nevertheless, I believe runzeo.bat would be a plus.
regards,
Senra <rsenra at acm.org>