From owner-freebsd-python@FreeBSD.ORG Tue Nov 28 15:41:56 2006 Return-Path: X-Original-To: freebsd-python@freebsd.org Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4838916A492; Tue, 28 Nov 2006 15:41:56 +0000 (UTC) (envelope-from dimma@higis.ru) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF21043CB2; Tue, 28 Nov 2006 15:41:52 +0000 (GMT) (envelope-from dimma@higis.ru) Received: from dimma (proxy-mow.oilspace.com [81.222.156.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 7EA88136CF6; Tue, 28 Nov 2006 15:41:53 +0000 (GMT) Received: from dimma (localhost [127.0.0.1]) by dimma (8.13.8/8.13.8) with ESMTP id kASFfqgd020702; Tue, 28 Nov 2006 18:41:52 +0300 (MSK) (envelope-from dimma@higis.ru) Date: Tue, 28 Nov 2006 18:41:52 +0300 From: Dmitriy Kirhlarov To: freebsd-python@freebsd.org, freebsd-ports@freebsd.org Message-ID: <20061128154151.GA6523@dimma.mow.oilspace.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 6.2-PRERELEASE User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: Subject: python ports management X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Nov 2006 15:41:56 -0000 Hi, list We are trying to update the TurboGear port to 1.0b1. For experiments I use non-system-default environment (auto-created by devel/porttools for me). 1. TurboGear 1.0b1 have different list of dependecies (it's not a big problem) 2. ... and I have to update some other ports and make several new (it's not a big problem, too) The problem is: 3. Some dependencies -- RuleDispatch for example have patchset and revision versions, OS release and architecture in their egg names. I think it's a bad idea -- supporting port with so unstable plist-name. 4. ... I try to use python setup.py install --single-version-externally-manage. It works, but fetches and installs all dependencies for RuleDispatch. This is bad because it bypasses the ports system. 5. ... I try to use python setup.py easy_install --no-deps. It works too, but installs egg with these crazy file names. 6. ... and I see no way for installing single version without dependencies (can't bealive) using easy_install 7. After reading some examples from ports tree I find that people patch setup.py to make it use distutils instead of easy_install. I think it's not the best way. Could somebody recommend me more proper way of using setuptools with the ports system? WBR Dmitriy