From owner-freebsd-python@FreeBSD.ORG Sat Aug 3 12:29:40 2013 Return-Path: <owner-freebsd-python@FreeBSD.ORG> 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 ESMTP id 0827FE54; Sat, 3 Aug 2013 12:29:40 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com [IPv6:2a00:1450:4013:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 64A332165; Sat, 3 Aug 2013 12:29:39 +0000 (UTC) Received: by mail-ee0-f51.google.com with SMTP id c1so784961eek.10 for <multiple recipients>; Sat, 03 Aug 2013 05:29:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=AnSWo2DrFmDnZdd5XmeHfoD645OZ3oxJItsNxLp7vZs=; b=xJO2vxbA3lccgQUOz3b94fuT+ufzPW3SCPB87zyUymrL74z8+OCCxALeLyhxtZU2QW 6w6pucQ+XCy2kRsQlEjsotC0VzIYc/LU0zN4LodIdPpmPHVWOzABXHVL/El3rpYCJ+cr EPeESUoCgunQRxjSCv781fLEitW5q/z3nv+8THi8paVHrxcDzrIfK0z+TvYi3zDy1vZd KZ6SXnYOUn+YsvCqIj3UHzZw3z3vhRuSZ/cpjw2sDsMdYoWnWZtZDdX1XDf9dzUrJaXv lblyKoXF8YE2saK3vXRyc7bW+xhg9imuvJRT9tUJgd2NdcEFhlr/XNob4BsGj77UWenG GiUQ== X-Received: by 10.14.214.136 with SMTP id c8mr9305454eep.6.1375532977487; Sat, 03 Aug 2013 05:29:37 -0700 (PDT) Received: from dragon.dg ([197.87.211.201]) by mx.google.com with ESMTPSA id k3sm19069940een.16.2013.08.03.05.29.35 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 03 Aug 2013 05:29:36 -0700 (PDT) From: David Naylor <naylor.b.david@gmail.com> To: freebsd-python@freebsd.org, Marcus von Appen <mva@freebsd.org> Subject: Re: Enabling ports to be installed for different python versions Date: Sat, 03 Aug 2013 14:29:29 +0300 Message-ID: <3135486.lOCflO8WFc@dragon.dg> User-Agent: KMail/4.9.5 (FreeBSD/9.1-RELEASE; KDE/4.9.5; amd64; ; ) In-Reply-To: <20130803103245.GA62768@medusa.sysfault.org> References: <20130803103245.GA62768@medusa.sysfault.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3157046.GBhVY2qg2y"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 03 Aug 2013 12:29:40 -0000 --nextPart3157046.GBhVY2qg2y Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote: > ...at the same time. > > Use PKGNAMEPREFIX/SUFFIX for python ports > > - this is a clean up task (which should be done regardless of everything > else). Some python modules miss the prefix, making it impossible to > install them for multiple python versions at the same time I think not all python based ports should use PKGNAMEPREFIX/SUFFIX. Those are ports who's main contribution is a bin/ and not libraries. In these cases the use of python is largely incidental. Two example are devel/eric4 (there is an eric5 that supports python3) and ports-mgmt/portbuilder. > Support for non-CPython implementations: > > - A mid-term goal should be to offer support PyPy in USE_PYTHON, etc. > This can introduce a new PYTHON_PKGNAMEPREFIX and SUFFIX and should > have only a minimal impact on implementing the change, once everything > else has been done. I don't think we need to limit the scope to only PyPy, there is also IronPython and Jython (perhaps longer term goals). I have the following suggestions for PYTHON_PKGNAMEPREFIX: - ppyXY for PyPy - p3pyXY for PyPy3 - ipyXY for IronPython - jpyXY for Jython where XY is the implementation version. > 4) Support for non-CPython implementations > > A rather small task; will mainly involve marking ports as not working > under PyPy. Can you please clarify this? Are you proposing: - marking all ports as not working under PyPy, or - those ports that fail to build/install under PyPy or - those ports that do not run under PyPy (this will require some form of testing the ports after installation). I'll happily act as liaison between the Python/FreeBSD PyPy teams if needed. Thank you for undertaking this fixup of python ports :-D Regards --nextPart3157046.GBhVY2qg2y Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlH896wACgkQUaaFgP9pFrKV/QCdE7QMWkJK7LZgoiJwb/oxmHaP P/0AnR59ThqLOf7S0Nq/wfoH0PpgZXGz =gEA6 -----END PGP SIGNATURE----- --nextPart3157046.GBhVY2qg2y--