From owner-svn-ports-head@freebsd.org Sun Apr 16 00:18:55 2017 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 31344D2A134; Sun, 16 Apr 2017 00:18:55 +0000 (UTC) (envelope-from osa@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0654A1394; Sun, 16 Apr 2017 00:18:55 +0000 (UTC) (envelope-from osa@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 975) id 2D040FF0; Sun, 16 Apr 2017 00:18:54 +0000 (UTC) Date: Sun, 16 Apr 2017 00:18:54 +0000 From: "Sergey A. Osokin" To: Ian Lepore Cc: Mathieu Arnold , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r438592 - in head/www/nginx-devel: . files Message-ID: <20170416001854.GN85682@FreeBSD.org> References: <201704151739.v3FHdat1041522@repo.freebsd.org> <626f1beb-0006-f9a8-82c2-5d8d03fb4b53@FreeBSD.org> <1492285633.62945.15.camel@freebsd.org> <20170415214049.GM85682@FreeBSD.org> <1492295503.62945.22.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1492295503.62945.22.camel@freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 16 Apr 2017 00:18:55 -0000 On Sat, Apr 15, 2017 at 04:31:43PM -0600, Ian Lepore wrote: > On Sat, 2017-04-15 at 21:40 +0000, Sergey A. Osokin wrote: > > On Sat, Apr 15, 2017 at 01:47:13PM -0600, Ian Lepore wrote: > > > > > > On Sat, 2017-04-15 at 21:32 +0200, Mathieu Arnold wrote: > > > > > > > > Le 15/04/2017 ? 19:39, Sergey A. Osokin a ?crit : > > > > > > > > > > > > > > > Author: osa > > > > > Date: Sat Apr 15 17:39:35 2017 > > > > > New Revision: 438592 > > > > > URL: https://svnweb.freebsd.org/changeset/ports/438592 > > > > > > > > > > Log: > > > > > š Remove IPV6 knob, IPv6 now compiled-in automatically if > > > > > support > > > > > is found. > > > > > šš > > > > Does this mean that if I build the package on a host without > > > > IPv6, it > > > > gets disabled and I don't get IPv6 support where I install the > > > > package ? > > > Even worse, if I build the package on a system with IPV6 enabled I > > > will > > > be unable to build the package with it disabled, > > Not true, It's possible to build an nginx package without IPv6 on a > > system > > with IPv6 enabled, please see http://hg.nginx.org/nginx/rev/a6d116645 > > c51 > > for details. > > But you removed the IPV6 knob rather than adapting it to the new way > upstream provides for en/disabling it. šHow does that enable me to > build without ipv6 support? No problem: .if ${.CURDIR:M*/www/nginx-devel} CONFIGURE_ARGS+="--with-cc-opt=\"-DNGX_HAVE_INET6=0\"" .endif Not tested yet. > I should note for the record that my concern here is theoretical... at > $work we ship products without ipv6 support enabled and (cross-)build > the packages on a machine that does have it enabled, but nginx is not > one of the packages, so this isn't impacting me directly. šBut if I > have such a need to create packages that don't match the build > machine's setup, it's reasonable to assume I'm not the only one. -- Sergey A. Osokin osa@FreeBSD.org