From owner-freebsd-python@FreeBSD.ORG Tue Jun 5 18:51:16 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 346A41065670; Tue, 5 Jun 2012 18:51:16 +0000 (UTC) (envelope-from mva@FreeBSD.org) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.freebsd.org (Postfix) with ESMTP id E31628FC1A; Tue, 5 Jun 2012 18:51:15 +0000 (UTC) Received: from [89.182.54.3] (helo=localhost) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1SbyqY-00072W-Bs; Tue, 05 Jun 2012 20:51:14 +0200 Date: Tue, 5 Jun 2012 20:53:09 +0200 From: Marcus von Appen To: Baptiste Daroussin Message-ID: <20120605185309.GA2956@medusa.sysfault.org> References: <20120605120755.GA71005@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20120605120755.GA71005@ithaqua.etoilebsd.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Df-Sender: MzAzMjU2 Cc: python@FreeBSD.org Subject: Re: Python conflicting with other python when installed from packages X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 05 Jun 2012 18:51:16 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Tue Jun 05, 2012, Baptiste Daroussin wrote: [...] > The thing is that they are conflicting only for the bin/2to3 file. It would be > nice if this file could be for example prefixed with the release of > python like: > > bin/py27-2to3 or something like that. I'm aware that when just installing from > ports only the first version of python installed got it, but if you > are thinking in package only world it can't works that way. In a package only world, I'll find ready-to-run packages for every python flavour I need. Hence I find a - py25-foobar - py26-foobar - py27-foobar ... - pyWHATEVER-foobar The good thing for me as a user is that I do not really need to rely on 2to3 anymore at installation time. $package-tool did that already for me. If I however am a developer and need $package-tool, I could live with the fact that $provider defines $version as default (just as we do it right now in bsd.python.mk). If I am not happy with their choice, I can use the ports. Simple as that. Prefix them on your own, define one as default for the packages and that's it. I do not see anyother implications. If a port should (for whatever ridiculous reason) rely on a certain bin/2to3 version at run-time, it'd need to be fixed in the ports tree, too. Cheers Marcus --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/OVZQACgkQi68/ErJnpkf/fQCgmBKp+f5Zor8W8TCYamK3eoOm jeEAoJNhwPQW2vcNua6oQJtavOEvBL5m =oWZR -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK--