From owner-freebsd-python@FreeBSD.ORG Mon Jul 25 10:13:57 2005 Return-Path: X-Original-To: python@freebsd.org 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 73E8716A41F for ; Mon, 25 Jul 2005 10:13:57 +0000 (GMT) (envelope-from filippo.natali@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94E2C43D60 for ; Mon, 25 Jul 2005 10:13:55 +0000 (GMT) (envelope-from filippo.natali@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so386862rne for ; Mon, 25 Jul 2005 03:13:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=GFqLsdCWEcbKP1rCljKDQJiYLyKuDd/86yoc5S9+VqDG10AsDLflPqcygF3+R8FnXE+Ll4JRU97Dj0lCzMt54/GSWockDe9KRx73qBmEEgq4G4TGzknmWJMuTStE1GHj8CkVVed+3WNOb3Q8HGK5rYayYoQlIMMuEg1LkTA9WVw= Received: by 10.11.118.18 with SMTP id q18mr46848cwc; Mon, 25 Jul 2005 03:13:54 -0700 (PDT) Received: by 10.11.116.18 with HTTP; Mon, 25 Jul 2005 03:13:54 -0700 (PDT) Message-ID: <8828e1ad05072503136d2a1260@mail.gmail.com> Date: Mon, 25 Jul 2005 10:13:54 +0000 From: Filippo Natali To: ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: python@freebsd.org Subject: BROKEN Zope products ports X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Filippo Natali List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2005 10:13:57 -0000 Hi, the package building problem with Zope products depending from python modules still stand from long time (since the introduction of python 2.4 as default version) and will be solved when Zope port will support python 2.4. The problem of double python dependency seems related only to the package building process, so I'm asking if skipping the package build adding NO_PACKAGE to these ports is a suitable workaround. regards, Filippo Natali