From owner-freebsd-python@FreeBSD.ORG Sat Aug 10 08:47:16 2013 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 26C357F7; Sat, 10 Aug 2013 08:47:16 +0000 (UTC) (envelope-from mva@FreeBSD.org) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D88212F7F; Sat, 10 Aug 2013 08:47:15 +0000 (UTC) Received: from [89.183.28.55] (helo=localhost) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1V84op-00074V-GX; Sat, 10 Aug 2013 10:46:39 +0200 Date: Sat, 10 Aug 2013 10:46:38 +0200 From: Marcus von Appen To: python@freebsd.org, portmgr@FreeBSD.org Subject: Re: [CFT] lang/python becoming a python binary wrapper Message-ID: <20130810084638.GB1282@medusa.sysfault.org> Mail-Followup-To: python@freebsd.org, portmgr@FreeBSD.org References: <20130802180059.GA1278@medusa.sysfault.org> <20130803123634.GA1280@medusa.sysfault.org> <20130803123914.GB1280@medusa.sysfault.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xgyAXRrhYN0wYx8y" Content-Disposition: inline In-Reply-To: <20130803123914.GB1280@medusa.sysfault.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Df-Sender: MTEyNTc0Mg== X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Marcus von Appen List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2013 08:47:16 -0000 --xgyAXRrhYN0wYx8y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The diff at http://people.freebsd.org/~mva/python-wrapper.diff was updated to include additional symlinks to bin/XXXX{2|3}, since those were missing in the previous patch, which could break some ports that use e.g. bin/python2 or bin/python3 on build time. One minor issue remains: lang/python right now deals only with either python2.X OR python3.X. This means that, if you have set 2.x as PYTHON_DEFAULT_VERSION and are going to install a python 3.x port, lang/python will not create a bin/python3 symlink. This can become an annoying inconsistency. The cleanest approach might be to create a lang/python3 meta port, which handles the different python 3.x versions correctly and either move lang/python to lang/python2 (for naming) or let lang/python deal only with the python2.X ports. To avoid unwanted side effects, I would go for lang/python3 and let lang/python deal with python2.X ports only. I'll create a lang/python3 meta port and, if everything works as expected and the impact on the ports tree is as low as possible, will commit it on the next weekend after the the 9.2 branch. Comments? Cheers Marcus --xgyAXRrhYN0wYx8y Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlIF/e4ACgkQi68/ErJnpkfawwCgy5bGrGPeTVtQvxGtePcKOz8U 4b4An1IN+E3onRi7nwd8PLEHbab2i3aZ =ekny -----END PGP SIGNATURE----- --xgyAXRrhYN0wYx8y--