From owner-svn-ports-head@freebsd.org Thu Jan 4 07:32:09 2018 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A7CFEA4EEB; Thu, 4 Jan 2018 07:32:09 +0000 (UTC) (envelope-from yuri@freebsd.org) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 57A857DBEB; Thu, 4 Jan 2018 07:32:08 +0000 (UTC) (envelope-from yuri@freebsd.org) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w047W8lQ004797 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 3 Jan 2018 23:32:08 -0800 (PST) (envelope-from yuri@freebsd.org) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Reply-To: yuri@freebsd.org Subject: Re: svn commit: r457997 - head/devel/py-cffi To: Antoine Brodin , tcberner@freebsd.org Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org References: <201801031838.w03IcgNc008075@repo.freebsd.org> From: Yuri Message-ID: Date: Wed, 3 Jan 2018 23:32:07 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 07:32:09 -0000 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