From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A56081381F3 for ; Fri, 14 Dec 2012 22:08:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08CF621C03F; Fri, 14 Dec 2012 22:08:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1F29721C03F for ; Fri, 14 Dec 2012 22:08:33 +0000 (UTC) Received: from pomiocik.lan (159-205-67-229.adsl.inetia.pl [159.205.67.229]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 0109533DCDC; Fri, 14 Dec 2012 22:08:30 +0000 (UTC) From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= To: gentoo-python@lists.gentoo.org Cc: python@gentoo.org, cpp@gentoo.org Subject: [gentoo-python] [PATCHes] boost migration to python-r1 Date: Fri, 14 Dec 2012 23:08:33 +0100 Message-Id: <1355522916-23815-1-git-send-email-mgorny@gentoo.org> X-Mailer: git-send-email 1.8.0.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 26b489e0-eba5-43d1-9aa0-4fb07bd7ee62 X-Archives-Hash: 03bfdd93cc1e863fc36d0dc51981f487 [Note: sending this mail to the ml to have it archived, actual maintainers are CC-ed.] I'd like to announce that I've prepared a batch of three patches which clean up the boost ebuild a bit and then migrate it to python-r1. A quick summary follows: (1) removes unnecessary setting of Python includedir and libdir in jam config. The bootstrap script does not write them there, and without them bjam finds Python libs and headers just fine. (2) just replaces three calls to $(python_get_sitedir) with a single one, storing the result in a variable. (3) does the actual migration. It's mostly replacing variables and functions with python-r1 counterparts, and moving the module optimization to build process. It's not much of a difference actually. Shortly saying, the ebuild is a compatible replacement, with all niceness of python-r1 installed (as in implementations being selectable via PYTHON_TARGETS). Any comments? Tiziano, would you mind if I committed this? -- Best regards, Michał Górny