devel/libffi and lang/python34

[Kubilay Kocak]

On 26/12/2014 3:53 PM, Robert Simmons wrote:
> I think the best option is A&C: to remove libffi from python and to
> update our port. The config choice itself can then be removed from the
> python port.
> 
> On Thu, Dec 25, 2014 at 11:37 PM, Kubilay Kocak <koobs at freebsd.org> wrote:
>> On 26/12/2014 3:06 PM, Robert Simmons wrote:
>>> The default for lang/python34 is to use libffi from ports. The version
>>> in ports is getting old (v3.0.13). The current version is v3.2.1.
>>> However, the version that ships with python 3.4.2 is 3.1.
>>>
>>> Should the default for python34 be changed to use the included version (v3.1)?
>>> _______________________________________________
>>> freebsd-ports at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>>>
>>
>> I'd like to see:
>>
>> a) The libffi port updated
>> b) libffi *not* be the default for Python ports
>>
>> We prefer to be as close to upstream as possible.
>>
>> c) See upstream Python not bundle libffi at all
>>
>> iirc, there's been mentions upstream of ripping libffi out in the past,
>> perhaps its worth re-starting that conversation
>>
>> koobs
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 

More precisely: I'd like to see (b) until (c) happens.

In the meantime I'm updating libffi.

Jump in #freebsd-python freenode if you'd like to talk more :)

./koobs