From owner-freebsd-python@FreeBSD.ORG Sun Feb 22 01:28:45 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA8C916A4CE; Sun, 22 Feb 2004 01:28:45 -0800 (PST) Received: from postman.arcor.de (postman2.arcor-online.net [151.189.0.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20C2143D1D; Sun, 22 Feb 2004 01:28:45 -0800 (PST) (envelope-from eikemeier@fillmore-labs.com) Received: from fillmore.dyndns.org (port-212-202-51-138.reverse.qsc.de [212.202.51.138]) (authenticated bits=0)i1M9Scf5019247 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 22 Feb 2004 10:28:39 +0100 (MET) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.30; FreeBSD) id 1Aupue-0009Xz-Bf; Sun, 22 Feb 2004 10:28:36 +0100 Message-ID: <40387643.9040805@fillmore-labs.com> Date: Sun, 22 Feb 2004 10:28:35 +0100 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Hye-Shik Chang , Khairil Yusof Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: FreeBSD Python Subject: USE_ZOPE vs. python modules X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2004 09:28:45 -0000 Dear maintainers, the breakage of www/zope-cmfphoto http://bento.freebsd.org/errorlogs/i386-4-full/zope-cmfphoto-0.4.r2.log seems to have roots in the current bsd.python.mk structure. Basically if you define USE_ZOPE in a port, you'll get Python 2.1 by default, if you just define USE_PYTHON You'll get Python 2.3. The result is that if a port that uses zope depends on an another that doesn't, you'll get different versions of the python modules (py21-imaging vs. py23-imaging in this case), which breaks installation. The workaround would be either to set the system-wide default to 2.1 or update zope to a version supporting 2.3. I am aware of the recent thread `Zope 2.6.4 vs 2.7', I just wanted to notify you because www/zope-cmfphoto is marked as BROKEN (and scheduled for removal), for reasons that lie beyond the responsibilites of this port (or its maintainer). Regards Oliver