From owner-freebsd-python@FreeBSD.ORG Mon Jul 29 09:05:39 2013 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A6659B3 for ; Mon, 29 Jul 2013 09:05:39 +0000 (UTC) (envelope-from mva@freebsd.org) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63FC9283C for ; Mon, 29 Jul 2013 09:05:39 +0000 (UTC) Received: from [80.67.16.112] (helo=webmailfront02.ispgateway.de) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1V3jOU-00052D-KD; Mon, 29 Jul 2013 11:05:30 +0200 Received: from his1.his.de (his1.his.de [192.124.237.237]) by webmail.df.eu (Horde Framework) with HTTP; Mon, 29 Jul 2013 11:05:30 +0200 Date: Mon, 29 Jul 2013 11:05:30 +0200 Message-ID: <20130729110530.Horde.8r2T8s2pSZ5xDoK1HOwi7Q1@webmail.df.eu> From: Marcus von Appen To: David Demelier Subject: Re: Dealing with 2.7 and 3.3 installations References: In-Reply-To: User-Agent: Internet Messaging Program (IMP) H5 (6.0.4) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc= Cc: freebsd-python@freebsd.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mva@freebsd.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 09:05:39 -0000 Zitat von David Demelier : > Hello, > > At the moment, it's very hard to install python 2.7 and 3.3 because of > the unification of the python ports. Also, pkgng will not let the user > install both the 2.7 and 3.3 version of the interpreter because it > will conflicts on several files such as /usr/local/bin/python for > example. This sounds like a pkgng issue to me with building lang/python the wrong way. Should be discussed with pkgng@ separately. > What I would like to propose, is to remove the non-versioned > binaries such as : > > /usr/local/bin/2to3 > /usr/local/bin/python > /usr/local/bin/python-config > > This should completely be removed from every version's pkg-plist. Then > we can create temporarly symlink in the pkg-install script if they are > not present. This is what /usr/ports/lang/python does. I do not see a problem here. > This will allow the installation of python 3.3 and python 2.7 at the > same time. This is already possible (see my post on ports@). Cheers Marcus