From owner-freebsd-python@FreeBSD.ORG Thu Sep 27 11:28:34 2012 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 186D4106566C; Thu, 27 Sep 2012 11:28:34 +0000 (UTC) (envelope-from demon@FreeBSD.org) Received: from elephant.yandex.ru (elephant.yandex.ru [77.88.34.7]) by mx1.freebsd.org (Postfix) with ESMTP id BCF038FC0A; Thu, 27 Sep 2012 11:28:33 +0000 (UTC) Received: from dhcp175-40-red.yandex.net (dhcp175-40-red.yandex.net [95.108.175.40]) by elephant.yandex.ru (Postfix) with ESMTP id 3XSDBn1VVjz45JpV; Thu, 27 Sep 2012 15:22:25 +0400 (MSK) Message-ID: <506436DB.90408@FreeBSD.org> Date: Thu, 27 Sep 2012 15:22:03 +0400 From: Dmitry Sivachenko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120903 Thunderbird/15.0 MIME-Version: 1.0 To: Li-Wen Hsu References: <5062AAEA.4000401@FreeBSD.org> <5062C5CB.4060109@yandex.ru> <5062C769.6090305@FreeBSD.org> <5062C8CE.701@yandex.ru> <5062E478.8020000@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Dmitry Sivachenko , 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: Thu, 27 Sep 2012 11:28:34 -0000 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). > > Li-Wen > 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.