From owner-freebsd-ports@freebsd.org Fri Sep 7 08:44:29 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49046FF4BD6 for ; Fri, 7 Sep 2018 08:44:29 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EA6680AA5 for ; Fri, 7 Sep 2018 08:44:28 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from excmbx-24.um.gwdg.de ([134.76.9.234] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.90_1) (envelope-from ) id 1fyCNN-0005tf-Bx; Fri, 07 Sep 2018 10:44:25 +0200 Received: from krabat.raven.hur (91.8.156.212) by EXCMBX-24.um.gwdg.de (134.76.9.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1531.3; Fri, 7 Sep 2018 10:44:24 +0200 Subject: Re: U[dating Bind912 wants ghostscript? To: "@lbutlr" , Yuet-nan Wong via freebsd-ports References: <227B398C-9070-45E8-9B96-858762750BC5@kreme.com> From: Rainer Hurling Message-ID: Date: Fri, 7 Sep 2018 10:44:24 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <227B398C-9070-45E8-9B96-858762750BC5@kreme.com> Content-Type: text/plain; charset="utf-8" Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Originating-IP: [91.8.156.212] X-ClientProxiedBy: EXCMBX-14.um.gwdg.de (134.76.9.225) To EXCMBX-24.um.gwdg.de (134.76.9.234) X-Virus-Scanned: (clean) by clamav X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2018 08:44:29 -0000 Am 07.09.18 um 09:46 schrieb @lbutlr: > I went to update my install of Bind9 and it wanted to install a lot o new things, including ghostscript (which I have been careful to keep off my system due to many remotely exploitable vulnerabilities and a lack of need). In fact, there were a lot of new packages it wanted to install which appear to all be depended on doxygen. > > Were does this dependency on doxygen come from, and why does that then want to install ghostscript and tex? > > > ===>>> bind912-9.12.1P2 >> (18) > > ===>>> The following actions will be taken if you choose to proceed: > Upgrade bind912-9.12.1P2 to bind912-9.12.2P1_2 > Upgrade json-c-0.13 to json-c-0.13.1 > Upgrade protobuf-c-1.3.0_1 to protobuf-c-1.3.1 > Install devel/doxygen devel/protobuf-c seems to be the culprit: OPTIONS_DEFINE= DOXYGEN OPTIONS_DEFAULT= DOXYGEN > Install print/ghostscript9-agpl-base > Upgrade poppler-data-0.4.8 to poppler-data-0.4.9 > Install print/tex-dvipsk > Install devel/tex-web2c > Upgrade zziplib-0.13.62_2 to zziplib-0.13.69_1 > Install print/texlive-texmf > Install print/tex-basic-engines > Install print/texlive-base > Install devel/t1lib > Install graphics/poppler > Upgrade nspr-4.19 to nspr-4.20 > Upgrade nss-3.38 to nss-3.39 > Install print/harfbuzz-icu > Install print/tex-formats > Upgrade protobuf-3.5.2,1 to protobuf-3.5.2_1,1 > > I looked in the make config for bin912 and didn't see anything that implied doxygen was needed, > > I went ahead and did postmaster -i bind912 and said no to Doxygen which meant the only things updated were bind, json, protobuff-c and protobuff. which is much more in line with what I was expecting. > > However, during the compile process, doxygen, ghostscript, and the various tex packages were installed anyway. > > What has changed in the build instructions for bind912? > >