Date: Wed, 3 Jan 2018 23:32:07 -0800 From: Yuri <yuri@freebsd.org> To: Antoine Brodin <antoine@freebsd.org>, tcberner@freebsd.org Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r457997 - head/devel/py-cffi Message-ID: <b2bc7e21-761d-17f9-0f93-5716d1713cb5@freebsd.org> In-Reply-To: <CAALwa8krgVa3A5JembcREbxvdA0qCW9KE3%2B0aH70fOn7KMiukQ@mail.gmail.com> References: <201801031838.w03IcgNc008075@repo.freebsd.org> <CAALwa8krgVa3A5JembcREbxvdA0qCW9KE3%2B0aH70fOn7KMiukQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/03/18 22:34, Antoine Brodin wrote: > How was this tested? I tested it with the new upcoming port devel/py27-llvmcpy. It works fine with the new version. > This breaks some ports depending on it and probably changes plist of > ports depending on it so some PORTREVISIONs should have been bumped. Which port/ports are breaking? py-cffi installs one shared library. I believe it only supports their own python modules, and isn't used directly by others. It also supplies headers. They are used by itself to build stub shared objects for native libraries, wrapped by cffi for use from python code. I just tried 3 depending ports security/py-bcrypt, devel/py-xattr, security/py-pynacl, and they all build fine. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b2bc7e21-761d-17f9-0f93-5716d1713cb5>