From owner-freebsd-python@FreeBSD.ORG Wed Sep 26 13:17:27 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 ED3B61065673; Wed, 26 Sep 2012 13:17:26 +0000 (UTC) (envelope-from mitya@yandex-team.ru) Received: from archeopterix.yandex.ru (archeopterix.yandex.ru [93.158.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 95E1F8FC0C; Wed, 26 Sep 2012 13:17:25 +0000 (UTC) Received: from Dmitrys-MacBook-Pro.local (v10-166-215.yandex.net [84.201.166.215]) by archeopterix.yandex.ru (Postfix) with ESMTP id 3XRfnq1pT2zrMnB; Wed, 26 Sep 2012 17:17:19 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1348665439; bh=bIu0s70VmBHUv3pAaEmEoU2CVxZGPFGtRnjPLFf5eus=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=Epi3vChCbibZFbg9baJiu+75nGdovjxMn3vIRxj2dIF8C9EOm62xyzJCGPG85NbCj IPai4iNfv/XmKffc3NgRvOtal6urOkzvY/idmYfmNdycM2WLHS5jD2xnFV4woS2DA5 a0+7hLLJfiJF24y65MliGZeI6pwNvp1rSEV8PsOk= Message-ID: <50630060.1030400@yandex-team.ru> Date: Wed, 26 Sep 2012 17:17:20 +0400 From: =?UTF-8?B?0JTQvNC40YLRgNC40Lkg0KHQuNCy0LDRh9C10L3QutC+?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 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: Wed, 26 Sep 2012 13:17:27 -0000 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. 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). Let maintainers take the final decision and implement it though.