From owner-freebsd-ports@freebsd.org Mon Feb 22 15:41:27 2016 Return-Path: Delivered-To: freebsd-ports@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 DD419AB0B6F for ; Mon, 22 Feb 2016 15:41:27 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 376611A73 for ; Mon, 22 Feb 2016 15:41:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA24975; Mon, 22 Feb 2016 17:41:24 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1aXsc0-0007Eh-JW; Mon, 22 Feb 2016 17:41:24 +0200 Subject: Re: unexpected package dependency To: Perry Hutchison References: <56c43d57.Pot24goK72QkTKqk%perryh@pluto.rain.com> <56C45B9C.7090808@FreeBSD.org> <56c6760d.nR7fjvuf3gEK3yNY%perryh@pluto.rain.com> Cc: freebsd-ports@FreeBSD.org From: Andriy Gapon Message-ID: <56CB2BD4.1040908@FreeBSD.org> Date: Mon, 22 Feb 2016 17:40:04 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56c6760d.nR7fjvuf3gEK3yNY%perryh@pluto.rain.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2016 15:41:28 -0000 On 19/02/2016 03:55, Perry Hutchison wrote: > Andriy Gapon wrote: >> On 17/02/2016 11:28, Perry Hutchison wrote: >>> I had not expected to find gcc listed (in packagesite.yaml) as a >>> dependency of the sysutils/cpuburn package. I can understand a >>> _port_ needing gcc (at build time), but does the cpuburn _package_ >>> actually require gcc at _runtime_? >> >> I don't believe so. AFAIR, it builds static binaries. > > So would the inclusion of gcc in the "deps" for sysutils/cpuburn (in > packagesite.yaml) be caused by a problem with the way the dependencies > are specified in the port, or with the way they are handled by the > package-generation mechanism? (I'm trying to figure out which to file > a PR against -- and I'm not all that familiar with pkgng details.) > My recollection is that the ports infrastructure does not allow to specify whether a non-base compiler (like GCC for FreeBSD 11) is required only as a compiler (that is, only during the build time) or if its run-time is required as well. The latter is always assumed. But I could be mistaken. -- Andriy Gapon