From owner-freebsd-python@FreeBSD.ORG Mon Oct 1 17:39:48 2012 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FB8E106564A; Mon, 1 Oct 2012 17:39:48 +0000 (UTC) (envelope-from lwhsu@FreeBSD.cs.nctu.edu.tw) Received: from FreeBSD.cs.nctu.edu.tw (FreeBSD.cs.nctu.edu.tw [140.113.17.209]) by mx1.freebsd.org (Postfix) with ESMTP id C62E38FC0C; Mon, 1 Oct 2012 17:39:47 +0000 (UTC) Received: by FreeBSD.cs.nctu.edu.tw (Postfix, from userid 1058) id EB67A61CE0; Tue, 2 Oct 2012 01:39:46 +0800 (CST) Date: Tue, 2 Oct 2012 01:39:46 +0800 From: Li-Wen Hsu To: Dmitry Sivachenko Message-ID: <20121001173946.GB4939@FreeBSD.cs.nctu.edu.tw> References: <5062AAEA.4000401@FreeBSD.org> <5062C5CB.4060109@yandex.ru> <5062C769.6090305@FreeBSD.org> <5062C8CE.701@yandex.ru> <5062E478.8020000@FreeBSD.org> <506436DB.90408@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline In-Reply-To: <506436DB.90408@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Chris Rees , python@freebsd.org, Ruslan Mahmatkhanov Subject: Re: bin/python3 symlink for python3X ports 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: Mon, 01 Oct 2012 17:39:48 -0000 On Thu, Sep 27, 2012 at 15:22:03 +0400, Dmitry Sivachenko wrote: > On 26.09.2012 17:00, Li-Wen Hsu wrote: > > > > I think this patch is good. And I am thinking about also modifying > > other lang/python{2,3}X ports, thus we may need to beware of > > confliction on bin/python{2,3} between lang/python2X or lang/python3X > > ports. It is not so common but still possible to have more then one > > lang/python2X or lang/python3X ports installed. Maybe we can use the > > same logic of bin/python installation (first wins). > > > > I beleive that the vast majority of python[23] users will be fine with the > latest version of the relevant branch. > Considered that and also not to over complicate things I propose to make > python2/python3 symlink only for the latest version: python2 -> python2.7 > and python3 -> python3.2 for now. > > And leave python31, python25, python26 untouched. Users who really need older > versions of python should explicitly require python version during startup. > > If it is OK for you, I can work out the final patch. I think it's OK, and one more this might be helpful in the future is adding a condition like: .if ${PYTHON_VERSION} == ${PYTHON_DEFAULT_VERSION} then install the symlink. Thanks for working on this, I am looking forward to your patch. -- Li-Wen Hsu http://lwhsu.org