From owner-freebsd-python@freebsd.org Sat Nov 14 20:30:14 2015 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF6FAA2F264 for ; Sat, 14 Nov 2015 20:30:14 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE3C71D56 for ; Sat, 14 Nov 2015 20:30:14 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by vkbq142 with SMTP id q142so9679771vkb.3 for ; Sat, 14 Nov 2015 12:30:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=b0aaed2iOShb64+Im/lRz3jM1ykNNVdY/to5+fjUyII=; b=A58UzikCRoYNQYxC36mkxep6Gz7SZdfRGoTuuiQH7IciV6jowkAxON35FueY86U/e+ lZecPkHBb4sAQy4K620jeInN32O4ToaAkl/WoyPT8vx+kkprsIA3TaBn1BR3Kz+UB+3+ wDxu0DYgFY/XTAA3AAPhtiqh19fdobsf5Sc6e/Me2rnPU3CEvyXf/yBC0Zf6DVWpGXIG Tje3h0ovgbgFoIpT+Hos3HHHmGxj/xNuKwW3bnXdQ51Yhrb2DaVnjldew1fYK78t+lYI Xc7Kd/qXdRpQ9A9Lg2WB6GC4JT9kpFmq01ictlocSWCgkKNl6OTOIj7x31JBfJ2mrrjJ o10g== MIME-Version: 1.0 X-Received: by 10.31.171.200 with SMTP id u191mr4563370vke.44.1447533013304; Sat, 14 Nov 2015 12:30:13 -0800 (PST) Sender: lwhsu.freebsd@gmail.com Received: by 10.31.178.79 with HTTP; Sat, 14 Nov 2015 12:30:13 -0800 (PST) Date: Sun, 15 Nov 2015 04:30:13 +0800 X-Google-Sender-Auth: hKGOrP7CsZY7dpQfZ8-F1B9foVo Message-ID: Subject: Version specified ports for separated standard Python modules From: Li-Wen Hsu To: FreeBSD Python Team Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 20:30:15 -0000 Hi, Just read this thread: https://lists.freebsd.org/pipermail/freebsd-python/2015-November/009061.html This inspire me that we probably can create ports for those separated standard Python modules, for each supported Python versions in the tree. That is, adding databases/py3[2-5]-sqlite3, also for databases/py-gdbm and x11-toolkits/py-tkinter. Adding these gives us packages and this benefits pkg users, saving their time and space to build from scratch. I also suggest these ports maintained by python@. How do the people on this list think? These ports should be straightforward, just slaves port with USES=python:X.Y . If no one objects, I can add them. BTW, a thing surprises me is that we don't have a pkg-message which hints users to install separated standard Python modules since python34. Does anybody knows why? I haven't touched lang/pytohn* for a while. I also found that python34 is directly added, not through `svn cp` from python33 (well, python33 itself is also not...) And, for the python-version-specified ports, I found now we have: devel/py-setuptools devel/py-setuptools27 devel/py-setuptools32 devel/py-setuptools33 devel/py-setuptools34 devel/py-setuptools35 These give us following packages: py27-setuptools-17.0 py27-setuptools27-17.0 py32-setuptools32-17.0 py33-setuptools33-17.0 py34-setuptools34-17.0 py35-setuptools35-17.0 I remember in the past, we add python-version-specified port using pyXY-foo format. For example, we have devel/py-dbus devel/py3-dbus in ports, which generate py27-dbus-1.2.0_1 py34-dbus-1.2.0_1 packages, so I think that the version suffix in port name is not really needed. Or will trimming that make some other conflicts? Any idea? -- Li-Wen Hsu http://lwhsu.org