[ZODB-Dev] Re: [Zodb-checkins] CVS: ZODB3/ZEO - mkzeoinst.py:1.18.8.2

[Tres Seaver]

Jeremy Hylton wrote:
> On Tue, 2004-02-17 at 16:11, Tres Seaver wrote:
> 
>>Update of /cvs-repository/ZODB3/ZEO
>>In directory cvs.zope.org:/tmp/cvs-serv16638/ZEO
>>
>>Modified Files:
>>      Tag: Zope-2_7-branch
>>	mkzeoinst.py 
>>Log Message:
>>
>>
>>  - mkzeoinstance should depend on being able to find ZODB, not Zope:
>>    received wisdom is that running the storage *without* the appserver
>>    code is safer / faster.
> 
> 
> Thanks, Tres.  Did you make this change on the trunk, too?

Nope, I didn't have a trunk checkout handy at the moment.  I will do 
that shortly.

> I'm not quite sure how people run this code, but is there a chance that
> the path would contain both a ZODB install and a Zope install.  If
> that's possible, then we need to be sure that we don't pick up the Zope
> install's ZODB.  Right now, the code will pick up the last ZODB found.

I don't know how to differentiate the two.  I *think* it would be 
sensible to break out of the search at the *first* ZODB found, as that 
will be the one in effect when importing.

I found the issue because I have a buildout which invokes mkzeoinst from 
the standalone ZODB3 version, and it wouldn't run.

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com