From owner-freebsd-python@FreeBSD.ORG Mon Oct 1 18:45:06 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 95DA9106564A; Mon, 1 Oct 2012 18:45:06 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B766C8FC08; Mon, 1 Oct 2012 18:45:05 +0000 (UTC) Received: by bkcjf20 with SMTP id jf20so4207426bkc.13 for ; Mon, 01 Oct 2012 11:45:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zOcVrBv5EnDz3nbq8fY4xG2MaBhGhuY7AX6/+9Pd/9w=; b=nj3BX3c2xMtDN70YZlEYedxEwuPa7qRWcHeBySkwib3fNbSMvwkncEKO3+9stoWSn+ TBecwAF2/x956Qo8al5K48SUG9RMo7X5LzIRxYldpwUEEpNRLmaEkH3zUgwvaxJwDTuE 0EPY4YGnSNU6tQueH1QmYP0tSbeKAHs4EyVsQ46hK95IYnriIGLoav+wDmoGgP9Bx3Ga 3Wvb4jjfNgHUtgziI4VnvAjm8ln1IRPisIidxeSDa0mm4+dAYusKhJL48CaN8sbYkbi9 7fLv97wVpa9ZldUqGKp/tnLFYTuXEEj9JtHX+2c8mCuhqrZqzlAACoJTcNeJodIt/kKM dayg== Received: by 10.204.6.25 with SMTP id 25mr513323bkx.126.1349117103413; Mon, 01 Oct 2012 11:45:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.10.141 with HTTP; Mon, 1 Oct 2012 11:44:33 -0700 (PDT) In-Reply-To: <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> <20121001173946.GB4939@FreeBSD.cs.nctu.edu.tw> From: Chris Rees Date: Mon, 1 Oct 2012 19:44:33 +0100 Message-ID: To: Li-Wen Hsu Content-Type: text/plain; charset=ISO-8859-1 Cc: Dmitry Sivachenko , 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 18:45:06 -0000 On 1 October 2012 18:39, Li-Wen Hsu wrote: > 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. > Yes. It means that a deliberate decision by the user has been made that that particular version is there. However, it is still possible to have the "first installed wins" logic using a pkg-install script instead of in the Makefile, this would solve the package problems. Are you interested if I were to implement that? Chris