From owner-freebsd-ports@FreeBSD.ORG Sun Oct 6 19:49:31 2013 Return-Path: Delivered-To: freebsd-ports@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 6FA2139B; Sun, 6 Oct 2013 19:49:31 +0000 (UTC) (envelope-from daamn.m@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A7DE62C58; Sun, 6 Oct 2013 19:49:30 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id m15so6288828wgh.33 for ; Sun, 06 Oct 2013 12:49:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=E9+Ipou8jXx95ThHly4/aD50HIc/3MBzo66QjzVio6I=; b=qFAD3laTS/XTQYXAB9M/cw0HZhC4EPVFM0UDkylNAEpXrgtuHPDK1YRPuuro5d/1/H eN+tGx1cD9sBA/2WKEJ+eZHgRVgXZPbr/HSgCDne0KgnSnSPioqYHaDYUmybMMQl4XQL DWKBGle0E7fL593iCuOObk60hqwPFBaRzhzCyOB+P4OB0dwJa91GJvvE4r/Uwr9v9e8a +jmajeMO7x5opi4xcbufVdn9mthvFfdHTmUbi0S/c9bzoD52BIoJN/KUoLy/1RPMIFQQ hKkD/G7sAPiYxvAJGGNJmG2Qav3HjBZ9n0IOCZWaw0XKuhNZfPhuXvENsjF920F1jTKB R+KA== MIME-Version: 1.0 X-Received: by 10.194.123.8 with SMTP id lw8mr2006254wjb.40.1381088969130; Sun, 06 Oct 2013 12:49:29 -0700 (PDT) Received: by 10.216.72.202 with HTTP; Sun, 6 Oct 2013 12:49:29 -0700 (PDT) In-Reply-To: <20131006104349.GA1367@medusa.sysfault.org> References: <20131006104349.GA1367@medusa.sysfault.org> Date: Sun, 6 Oct 2013 21:49:29 +0200 Message-ID: Subject: Re: Installing ports for different versions of Python From: Daamn M To: Marcus von Appen , Daamn M , freebsd-python@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 19:49:31 -0000 2013/10/6 Marcus von Appen > On, Sat Oct 05, 2013, Daamn M wrote: > > > Hi, > > > > Sorry if I'm asking a question that have been asked many times but I > > couldn't find an answer using google. > > > > I need to install few version of Python (at least 2.6, 2.7 and 3.3). I > > really appreciate that FreeBSD let me have many versions the same time. > But > > I have a problem when I need some third party library. It turns out that > I > > can have only one instance. > > > > For example: I have installed python 2.7 and then port py-someport. Then > I > > installed python 3.3 and set PYTHON_DEFAULT_VERSION to point python 3.3. > If > > I try to install port py-someport again I wll get an error message saying > > that an older version is already installed. > > This is a limitation in package handling at the moment. The FreeBSD > ports tree unfortunately uses the origin (e.g. devel/py-someport) to > check, if a port was already installed, instead of e.g. the package name > (e.g. py33-someport, py27-someport, etc.). > > This is something being out of scope of the FreeBSD python team, but we > hope for a change of that behaviour in the near future. > Do you know something more about this future? Is there any real work done to change it? I would appreciate a link if you know. > > > The way a port is registered in the database suggest that there could be > > more than one version. I mean: port py-someport is registered as > > py27-someport when installed for python 2.7. > > > > Now I copy ports adding versio prefix. For example to install py-someport > > for version 3.3 I copy the port as py33-someport. I works pretty well > but I > > don't find it a clean way. > > > > Could you help? > > Your best chance at the moment would be to use virtualenv, if > possible. Most python packages feature pip support, so that you could > > 1) change to your specific virtualenv > 2) pip install > (or easy_install ) > 3) work in your virtualenv Cheers > Marcus > I think I will do it that way. But it would be nice to manage with packages from the OS level. Thanks for your comment Regards, Putrycy