From owner-freebsd-python@FreeBSD.ORG Mon Oct 1 17:33:47 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 B0537106566C; Mon, 1 Oct 2012 17:33:47 +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 7635B8FC0A; Mon, 1 Oct 2012 17:33:47 +0000 (UTC) Received: by FreeBSD.cs.nctu.edu.tw (Postfix, from userid 1058) id 606C461CC9; Tue, 2 Oct 2012 01:26:34 +0800 (CST) Date: Tue, 2 Oct 2012 01:26:34 +0800 From: Li-Wen Hsu To: =?big5?B?x/fIYsheyGjIZsheyF8gyEbIXshXyFXIbchayGPIYMhk?= Message-ID: <20121001172631.GA4939@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> <50630060.1030400@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <50630060.1030400@yandex-team.ru> User-Agent: Mutt/1.5.21 (2010-09-15) 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: Mon, 01 Oct 2012 17:33:47 -0000 On Wed, Sep 26, 2012 at 17:17:20 +0400, Ç÷ÈbÈ^ÈhÈfÈ^È_ ÈFÈ^ÈWÈUÈmÈZÈcÈ`Èd wrote: > On 9/26/12 5:00 PM, 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 actually dislike the current "first wins" logic. I hit that problem > recently. To be honest, I also realized this would cause problems just after sending my previous mail. This would generate conflicting packages of python[23]*. This definitely needs to be fixed. I apologize of committing this bug (three years ago!) > I think this choice should be done via make.conf variable (with some > default value hardcoded in bsd.python.mk). > The resulting packages should not depend on the order two pythons are > installed in. > (probaly defaulting python -> python2.X is the proper choice). This is what we did originally, and I thought what Josh said is reasonable: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/109550 I'm still thinking about a good solution, any suggestions? My current thought is there might be no perfect solution of this, and what ${PYTHON_DEFAULT_VERSION} defined should get /usr/local/bin/python, any other ports need specified version python should modify their shebang with ${PYTHON_CMD}. > Let maintainers take the final decision and implement it though. I think that all people on this list are the maintainers, the only difference is some of us having commit bit and need to serve others more. :) -- Li-Wen Hsu http://lwhsu.org