From owner-svn-ports-head@freebsd.org Sat Apr 15 22:31:47 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 C7B99D3FDBB for ; Sat, 15 Apr 2017 22:31:47 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 A8783F51 for ; Sat, 15 Apr 2017 22:31:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 57bdec0d-222b-11e7-bfb5-0d159cd3c324 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 57bdec0d-222b-11e7-bfb5-0d159cd3c324; Sat, 15 Apr 2017 22:32:01 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v3FMVh0h002303; Sat, 15 Apr 2017 16:31:43 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1492295503.62945.22.camel@freebsd.org> Subject: Re: svn commit: r438592 - in head/www/nginx-devel: . files From: Ian Lepore To: "Sergey A. Osokin" Cc: Mathieu Arnold , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Date: Sat, 15 Apr 2017 16:31:43 -0600 In-Reply-To: <20170415214049.GM85682@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> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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: Sat, 15 Apr 2017 22:31:47 -0000 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? 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. -- Ian > > > > then when it tries to > > run on a system without ipv6 support, it fails or spews > > error/warning > > messages.