From owner-freebsd-python@FreeBSD.ORG Sun Aug 11 10:37:37 2013 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09401F6A; Sun, 11 Aug 2013 10:37:37 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 46F7C2E7D; Sun, 11 Aug 2013 10:37:36 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id x12so4609988wgg.0 for ; Sun, 11 Aug 2013 03:37:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OLmc2ig+qvmTTMN5l1IWVHzX9mX3IrtA3jETrFPOBMo=; b=hdhB6Uo1NMSVhaJD2taH9QJtMAmJCNNc/UthxD/FzkKJ7hoTLC0zsC1araKGD0116N GOdArpPe4RmbUTEfZ8ZNy4Qy8weUHNICR92/xyKruJ3B1dh7F/A6lgBjqa/vCsPxu3li 25AkrwnqO9N+34+jx+5aGv17opHi/ZFgM8Aj0dYxZhr3OE8uqq/iRGo4F91a0lzDXkpg aOPpLFwHNN5Bima521BJmkCgNoWnCKLvxcI7uC8O6QPdr79kc3duVSuVPtmYvmbpJ9RM pvU2ANFAnv1ygtxLStnLYjyQlDnVRecn662ki5P/ic4N5YWHaopurR9WhE9slDCWmmYc Y76A== MIME-Version: 1.0 X-Received: by 10.180.13.83 with SMTP id f19mr4067339wic.54.1376217454667; Sun, 11 Aug 2013 03:37:34 -0700 (PDT) Received: by 10.194.239.164 with HTTP; Sun, 11 Aug 2013 03:37:33 -0700 (PDT) In-Reply-To: <20130810084638.GB1282@medusa.sysfault.org> References: <20130802180059.GA1278@medusa.sysfault.org> <20130803123634.GA1280@medusa.sysfault.org> <20130803123914.GB1280@medusa.sysfault.org> <20130810084638.GB1282@medusa.sysfault.org> Date: Sun, 11 Aug 2013 12:37:33 +0200 Message-ID: Subject: Re: [CFT] lang/python becoming a python binary wrapper From: David Demelier To: Marcus von Appen , python@freebsd.org, portmgr@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Aug 2013 10:37:37 -0000 2013/8/10 Marcus von Appen : > 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 Thanks for the work, I'll try that this during the week :-). Cheers, -- Demelier David