From owner-freebsd-python@FreeBSD.ORG Tue Jan 23 11:50:32 2007 Return-Path: X-Original-To: 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 9F53C16A402; Tue, 23 Jan 2007 11:50:32 +0000 (UTC) (envelope-from alexbl@FreeBSD.org) Received: from cherenkov.geekfire.com (cherenkov.geekfire.com [66.206.86.94]) by mx1.freebsd.org (Postfix) with ESMTP id 817EA13C478; Tue, 23 Jan 2007 11:50:32 +0000 (UTC) (envelope-from alexbl@FreeBSD.org) Received: from localhost.my.domain (c038h213.dorm.reed.edu [134.10.38.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by cherenkov.geekfire.com (Postfix) with ESMTP id 4023339F66; Tue, 23 Jan 2007 03:29:20 -0800 (PST) From: Alexander Botero-Lowry To: pav@FreeBSD.org In-reply-to: <1169549704.6221.10.camel@pav.hide.vol.cz> References: <20070123104738.GA41157@qlovarnika.bg.datamax> <1169549704.6221.10.camel@pav.hide.vol.cz> Comments: In-reply-to Pav Lucistnik message dated "Tue, 23 Jan 2007 11:55:04 +0100." Date: Tue, 23 Jan 2007 03:31:29 -0800 Sender: alex@localhost X-Peer: 127.0.0.1 Message-Id: <20070123112924.4023339F66@cherenkov.geekfire.com> Cc: gnome@FreeBSD.org, vd@FreeBSD.org, python@FreeBSD.org, ports-developers@FreeBSD.org Subject: Re: The way to fix ports/104560 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, 23 Jan 2007 11:50:32 -0000 > > Please take a look at ports/104560 (and also ports/105853 and > > ports/106120) and come to a consensus what is the right way to fix this > > issue. > >=20 > > I am sure we can come to an agreement and shortly commit a fix. > > As I see it: > > - lang/python metaport must be removed > - all lang/python2? ports will install $PREFIX/bin/python binary > > How that sounds? > > Or if people absolutely need to have several different pythons on a > system, make the bin/python automatical symlink, like in perl ports. This fails to deal with installing the site-packages in the appropriate site-package directories. The same site-package directory can't be used because the pyc and pyo format changes between python implementations, so python needs to be able to generate the appropriate wants per python installation. For ports that use USE_PYDISTUTILS (which is the most common way to install a python package) ${PYTHON} is used, so I don't see why other ports shouldn't follow the convention. I do _agree_ that something should always be installed as python, without version, but that doesn't mean that ports should just assume python when installing. They should use ${PYTHON} to be safe, and to make sure things are installed where the user wants them to be installed.