On 10/27/05, Sascha Ottolski <[EMAIL PROTECTED]> wrote:
Am Donnerstag, 27. Oktober 2005 13:20 schrieb Jens Vagelpohl:
> You just noted one more disadvantage yourself: The system Python is
> likely to be out of step with what Zope wants. Furthermore, updates
> to the system Python or to add-on packages might have unintended
> consequences for your Zope setup.

well, "might have" is one thing, really experiencing problems is quite

Well, I've had severe problems with zope based on an redhat-package,. This was, however, back in 8.0 and 9.0 version of Redhat. Things may have improved.
Basically the rpms we used were unstable (our site would crash on random acts (or so it seemed to us)), also on a couple of occations installing other rpms (not from redhat though), would break the python from redhat.
This and other bad experiences with redhat/rpms led to a policy with debian and compiled python/zope. I've never looked back.
The decision of throwing out redhat and rpms may have been based on my lack of knowledge or incompetence, but I will note that since switching to source-based zope and python (three years or so) and debian we've never experienced any problems that could not be solved within minutes.
Except one: We still have a POSKEY error in our Data.fs introduced with the old rpm-based install. I've never managed to delete or locate the object, but it doesn't seem to cause any trouble. So it stays. Just to remind me never to use redhat or rpms.

Just my two cents.

Einar Næss Jensen
tlf: +47 90990249
Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to