[CFT] lang/python becoming a python binary wrapper
The BSD Dreamer
beastie at tardisi.com
Sun Aug 18 13:53:31 UTC 2013
On 2013-08-17 09:55, Marcus von Appen wrote:
> On 17.08.2013, at 11:22, Kubilay Kocak <koobs.freebsd at gmail.com> wrote:
>
>> On 17/08/2013 7:01 PM, Marcus von Appen wrote:
>>> On, Sat Aug 17, 2013, Kubilay Kocak wrote:
>>>
>>>> On 17/08/2013 6:13 PM, Marcus von Appen wrote:
>>>>> The relevant UPDATING entry for the change will look like:
>>>>>
>>>>> 20130817:
>>>>> AFFECTS: users of lang/python*
>>>>> AUTHOR: mva at FreeBSD.org
>>>>>
>>>>> The lang/python* ports do not install links to 2to3, idle, pydoc,
>>>>> python
>>>>> and other binaries anymore. Those were moved into the lang/python2 and
>>>>> lang/python3 ports. If you have lang/python2* or lang/python3*
>>>>> installed,
>>>>> please also install the associated lang/python2 or lang/python3 port.
>>>>>
>>>>> 1. update lang/python2* and/or lang/python3*
>>>>> 2. install lang/python2 and/or lang/python3
>>>>> 3. reinstall lang/python (if installed).
>>>>>
>>>>>
>>>>> I think, the instructions should suffice. Please let me know, if you
>>>>> feel that more details are necessary.
>>>>>
>>>>> Cheers
>>>>> Marcus
>>>>
>>>> Minor tweak:
>>>>
>>>> The lang/python* ports no longer install links to 2to3, idle, pydoc,
>>>> python and other binaries. These have been moved into lang/python2 and
>>>> lang/python3 ports respectively. This change allows ... brief
>>>> explanation of benefit here.
>>>>
>>>> Also, what are the "other" binaries, and are they worth mentioning
>>>> explicitly?
>>>
>>> They are not worth mentioning in my opinion, since those would be the
>>> shared builds (python-shared) and config binaries
>>> (python-{shared}-config).
>>>
>>> Right now I would not want to name any specific benefit, since this
>>> could give users the wrong impression that it is available already and
>>> something like
>>>
>>> This change allows the FreeBSD python ports to be used with different
>>> Python versions at the same time as a mid-term goal.
>>>
>>> or
>>>
>>> This change will enable other Python implementations to act as default
>>> Python interpreter in the future.
>>>
>>> feels to vague to me. If you think, it's worth mentioning, I'll put it
>>> in, though.
>>>
>>> Cheers
>>> Marcus
>>
>> Concur, it ought to be clear. How's this:
>>
>> This change brings us closer to the goal of making Python ports usable
>> with different Python versions at the same time.
>>
>
> Sounds good, thanks.
What wasn't clear was that this applied to everybody, whether they knowingly
installed lang/python2* or lang/python3*, or not. Since, installing a port
that wants the python results in lang/python27 being installed by default
(and still does.)
So, when I tried updating www/firefox with portmaster this morning, it broke
python for everything by updating only lang/python27 for me. What happens to
the many other fresh systems when somebody builds their first port that pulls
in the default python, which is lang/python27, but that's not enough for
satisfy the dependency?
--
Name: Lawrence "The Dreamer" Chen Call: W0LKC
Snail: 1530 College Ave, A5 Email: beastie at tardisi.com
Manhattan, KS 66502-2768 Blog: http://lawrencechen.net
More information about the freebsd-python
mailing list