[zope2-tracker] [Bug 143760] Re: repozo should be in skel

[Justin Alan Ryan]

I'm just saying, as long as there's a mkzeoinstance script, I think it
should create a repoze script within that instance.

When using virtualenv, buildout, or possibly system-wide, the egg
totally is fine.  From time to time, it can be handy to install zeo by
itself.  Obviously, a special buildout or handcrafted virtualenv can be
created for dedicated zeo servers, I just don't see why mkzeoinstance
wouldn't do it, or why there would be opposition to me putting forth the
effort.

Maybe this is invalid for Zope2, but appropriate for zope.mkzeoinstance?
If the package becomes deprecated entirely, then it's irrelevant, but
otherwise, at least the wishlist status you set a week or two ago seems
reasonable.

This just doesn't seem driven by immense decisiveness about the future
roadmap, it seems driven by keeping the number of open bugs low.  There
is still a lot of code in the wild depending on older versions of Zope2
which could accept this, as well.

It's not a huge pain, but I don't think it's an invalid concern,
entirely.  I have at least twice in the past 18 months had dedicated zeo
servers which had to be brought up in a hurry and mkzeoinstance can be
handy.  It's not killing me to manually create the script as I decided
above, and the collective.recipe.backup better handles multiple ZODBs,
but it's not a worthless functionality, entirely.

-- 
repozo should be in skel
https://bugs.launchpad.net/bugs/143760
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.