[CFT] lang/python becoming a python binary wrapper

Dmitry Sivachenko trtrmitya at gmail.com
Mon Sep 16 14:54:08 UTC 2013


Hello,

Imagine the following scenario:
I have both python2 and python3 installed.
I want python2 to be the default version (lang/python port installs python -> python2.7, etc).

Then I want to build another port with python3 dependency.

I put USE_PYTHON=3.3+ in port's Makefile, but it depends on lang/python which pulls python2.7 too.

How can I build a python module with 3.X only dependency?

Thanks.


On 02.08.2013, at 22:00, Marcus von Appen <mva at FreeBSD.org> wrote:

> Dear all,
> 
> as discussed previously on this list, users would love to install the
> same python for multiple python versions.
> 
> Besides other issues (which I'll summarize in a different mail), one
> problem, especially for binary packages, are the "am I the default?"
> assumptions of lang/pythonXX.
> 
> The attached patch moves that logic into lang/python, instead of
> maintaining the IF_DEFAULT magic within the individual python ports.
> This will allow binary packages to be installed side by side without any
> hacks, but also requires users, which are now happily using
> /usr/local/bin/python (being created by lang/pythonXX) to install
> lang/python explicitly (UPDATING entry should be sufficient).
> 
> If there are no objections, I'll commit the change on the next weekend
> (09.08.+). Please take your time to test. If portmgr@ feels this might
> be a bit risky (ports implying /usr/local/bin/python based on
> lang/pythonXX), please issue an exp-run beforehand.
> 
> Cheers
> Marcus



More information about the freebsd-python mailing list