Date: Thu, 25 Dec 2014 23:53:22 -0500 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-ports@freebsd.org, zeising@freebsd.org, freebsd-python@freebsd.org Subject: Re: devel/libffi and lang/python34 Message-ID: <CA%2BQLa9DYw1U6ysJMYJ=iH4q90iQiApERpxLguBG-boz_B9mNLg@mail.gmail.com> In-Reply-To: <549CE605.5000209@FreeBSD.org> References: <CA%2BQLa9CDuJpHK1L8GvjySpCb1Bkoy2tNDLUUjWDJXEscW1_hfA@mail.gmail.com> <549CE605.5000209@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9DYw1U6ysJMYJ=iH4q90iQiApERpxLguBG-boz_B9mNLg>