From owner-freebsd-python@FreeBSD.ORG Wed Dec 18 07:55:15 2013 Return-Path: Delivered-To: freebsd-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 ESMTPS id A11A4DAC; Wed, 18 Dec 2013 07:55:15 +0000 (UTC) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.29.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C48A1186; Wed, 18 Dec 2013 07:55:15 +0000 (UTC) Received: from [89.183.19.185] (helo=localhost) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1VtBxB-0001ZU-8P; Wed, 18 Dec 2013 08:54:01 +0100 Date: Wed, 18 Dec 2013 08:54:01 +0100 From: Marcus von Appen To: Shane Ambler , bug-followup@FreeBSD.org Subject: Re: ports/184954: Installation checks prevent multiple python ports being installed Message-ID: <20131218075401.GA1379@medusa.sysfault.org> Mail-Followup-To: Shane Ambler , bug-followup@FreeBSD.org, freebsd-python@FreeBSD.org References: <201312180215.rBI2F0W3005666@oldred.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <201312180215.rBI2F0W3005666@oldred.freebsd.org> User-Agent: Mutt/1.5.22 (2013-10-16) X-Df-Sender: MTEyNTc0Mg== Cc: freebsd-python@FreeBSD.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 18 Dec 2013 07:55:15 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Wed Dec 18, 2013, Shane Ambler wrote: [...] > Recent changes cause py-setuptools to be installed for the python > version being used. The installation checks prevent py-setuptools being > installed for more than one python version at a time. > > > eg py27-setuptools prevents py32-setuptools being installed. > > I think the previous behaviour saw py27-setuptools and it was used > during install. Now I can't install a port set to use python32 or > python33 because setuptools is installed for python27. > > I've created duplicate ports to be able to install py-numpy for > multiple python versions but I don't want to start duplicating every > python port to support multiple python versions. This is a long-standing issue that the Python team is aware of. In fact, it does not only have an impact on python ports, but on all ports. The root cause is pkg_add, which uses the PKGORIGIN to detect, whether the port is installed. Since py32-setuptools and py27-setuptools both share the same PKGORIGIN (devel/py-setuptools), pkg_add fails. pkg shares the same problem by checking for the PKGORIGIN record, so a switch to pkg would not help you either. Right now there is no solution at hand for that problem, but we are working on it. --KsGdsel6WgEHnImy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlKxVJkACgkQi68/ErJnpkdz0ACcCiD6gv9uk3FHJz0zc4LomKKV uCwAn20mAx/wsu2U38pgHT4T+2JSn7pz =vwIe -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--