From owner-freebsd-python@FreeBSD.ORG Fri Dec 26 04:53:23 2014 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EB6B5AAA; Fri, 26 Dec 2014 04:53:23 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6159101D; Fri, 26 Dec 2014 04:53:23 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id w7so7113559qcr.14; Thu, 25 Dec 2014 20:53:22 -0800 (PST) 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=251zp+sOiVjNTr3REv8h+LYJtct7JaQDH6i73jtUYvI=; b=yVFysn71xE5x7gDOinFdJe3EN5n82vCXuAe9MAkS2lLRz0Z3H9RYpk0q6t8SZ/qDQW yyr/3vrOKwSAUHMjc4yQTqPONC4/MnbTLz/wdU+F0tzABTTEYxboFokPGFhcZU4WeUO+ GNUwZ7M/370Ky3d+Kqztm5Z/3kCl9hxGqY/Tfpy1/2UF/tbFrAShoOUzNsAKdq/xKUDH 5VMbWg8AChfLdoGarQXMcYY+sjdf23AZ2wEFC1Wpswqm8No6lFus/051VOnckU6ydNIR 7HE+tQ5H43t6b1JYu4YH1m8DFMbV7Kl8+CWWsUpKtvyYRP8BcQ7EDSFroGHUzijJrPU1 zjdw== MIME-Version: 1.0 X-Received: by 10.224.130.198 with SMTP id u6mr34059070qas.9.1419569602863; Thu, 25 Dec 2014 20:53:22 -0800 (PST) Received: by 10.140.18.145 with HTTP; Thu, 25 Dec 2014 20:53:22 -0800 (PST) In-Reply-To: <549CE605.5000209@FreeBSD.org> References: <549CE605.5000209@FreeBSD.org> Date: Thu, 25 Dec 2014 23:53:22 -0500 Message-ID: Subject: Re: devel/libffi and lang/python34 From: Robert Simmons To: freebsd-ports@freebsd.org, zeising@freebsd.org, freebsd-python@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2014 04:53:24 -0000 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 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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@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