From owner-freebsd-questions@FreeBSD.ORG Thu Nov 7 01:17:05 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0C668A73 for ; Thu, 7 Nov 2013 01:17:05 +0000 (UTC) (envelope-from kyle@ktdassoff.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1D1B2E2F for ; Thu, 7 Nov 2013 01:17:04 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id ED9A621803 for ; Wed, 6 Nov 2013 20:17:01 -0500 (EST) Received: from web5 ([10.202.2.215]) by compute3.internal (MEProxy); Wed, 06 Nov 2013 20:17:01 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=ktdassoff.net; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date; s=mesmtp; bh=4MzWxQiclphRcb2qnQIYxwH H73o=; b=yFj5U98q/zidYlWoHDbFN97DkBoUX/agypBF0HAWeC+ddomxnERO5Eq uLZiHQ20MlrVQnpsA/qNWtZUGoDJ7+6LoUu1JtqlJABBA8ou7fndMa8xoReoBemg 7LB+heAheG2ms8eSQCoi/0nwAUdY/GoMTOVxnJF/3bruiIpaxO/4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=4MzWxQiclphRcb2qnQIYxwHH73o=; b=LyD6r1C/MJtQSsd1LmQRckGa1S4f CYoZAXmzvP8LziMJPCv1TiSKVGfBTlRcueitX2j81nzE8o5MLTOrOGft50cgkHtz oKxLaekf1oICSWt0pGE6wWGpl5fBKHdS3FchjfSdVQy3GsnGx6L7i+Xij4cCSXwK 1Wl3L8TD9vXr6t8= Received: by web5.nyi.mail.srv.osa (Postfix, from userid 99) id CE636D60B86; Wed, 6 Nov 2013 20:17:01 -0500 (EST) Message-Id: <1383787021.13461.44104609.0336D6C2@webmail.messagingengine.com> X-Sasl-Enc: wFHYFrS6DrxXMUy4Suv+Jm5/HeXcoUblmPtW5gdZ7b6X 1383787021 From: KT Dassoff To: FreeBSD Questions MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488 Subject: Parallel Python packages for different versions w/ pkgng Date: Wed, 06 Nov 2013 19:17:01 -0600 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 01:17:05 -0000 Hey all, I had a question about installing multiple copies of Python packages from ports for different versions of Python (e.g. installing Sphinx for both Python 2.7 and Python 3.3). Now, I know to set the PYTHON_VERSION environment variable when building the appropriate py-* port. And the generated package will have the expected prefix (i.e. py27-* or py33-* etc). The problem is that ports/pkgng will treat a py27-* package and a py33-* package as different versions to be upgraded even though, as far as I know, they install their files to different site-packages trees according to the interpreter they're built for, and if I recall, this worked fine with the older package infrastructure. Example: * Install `textproc/py-sphinx` with no PYTHON_VERSION set (equivalent to =2.7); that succeeds, and `pkg info` later shows py27-sphinx installed * Install the same port with PYTHON_VERSION set to 3.3; the port will build fine, but when running `make install` (whether directly or via portmaster), it will try to replace py27-sphinx with py33-sphinx by deinstalling py27-sphinx before installing the py33 version Is there something else I need to do to install them side-by-side, or is this some bug in pkgng, or is there some actual conflict between Python packages via ports that I'm not aware of?