From owner-svn-ports-head@freebsd.org Thu Apr 27 23:58:16 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 11661D53CF4; Thu, 27 Apr 2017 23:58:16 +0000 (UTC) (envelope-from osa@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 E56F4337; Thu, 27 Apr 2017 23:58:15 +0000 (UTC) (envelope-from osa@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 975) id 161F956A0; Thu, 27 Apr 2017 23:58:15 +0000 (UTC) Date: Thu, 27 Apr 2017 23:58:15 +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: r439421 - in head/www/nginx: . files Message-ID: <20170427235815.GH18747@FreeBSD.org> References: <201704252318.v3PNI9Io032993@repo.freebsd.org> <20170426165333.GC18747@FreeBSD.org> <1426aa14-e30f-bb33-6e76-5fdfdd222e74@FreeBSD.org> <20170427164627.GE18747@FreeBSD.org> <1493312147.66427.6.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1493312147.66427.6.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: Thu, 27 Apr 2017 23:58:16 -0000 On Thu, Apr 27, 2017 at 10:55:47AM -0600, Ian Lepore wrote: > On Thu, 2017-04-27 at 16:46 +0000, Sergey A. Osokin wrote: > > On Thu, Apr 27, 2017 at 08:24:55AM +0200, Mathieu Arnold wrote: > > > > > > Le 26/04/2017 ?? 18:53, Sergey A. Osokin a ??crit : > > > > > > > > On Wed, Apr 26, 2017 at 06:18:44PM +0200, Mathieu Arnold wrote: > > > > > > > > > > Le 26/04/2017 ?? 01:18, Sergey A. Osokin a ??crit : > > > > > > > > > > > > Author: osa > > > > > > Date: Tue Apr 25 23:18:09 2017 > > > > > > New Revision: 439421 > > > > > > URL: https://svnweb.freebsd.org/changeset/ports/439421 > > > > > > > > > > > > Log: > > > > > > š Upgrade from 1.10.3 to 1.12.0. > > > > > > šš > > > > > > š ChangeLog: http://nginx.org/en/CHANGES-1.12 > > > > > > šš > > > > > > š Remove IPV6 knob, IPv6 now compiled-in automatically if > > > > > > support is found. > > > > > This still feels like a very bad idea. > > > > Could you please explain what exactly is very bad here? > > > We had that talk like a week or two ago. It means that if the > > > package > > > builder support IPv6 it will not work on a box without it, and if > > > the > > > package builder does not support IPv6, a box with IPv6 will not be > > > able > > > to use nginx with IPv6. > > Then you can go ahead and enable IPv6 on the package builder like you > > did the > > same for the third-party moz_zip module. > > > > INET6 in FreeBSD's GENERIC kernel for years, I see no reason why > > shouldn't use it. > > Why do you continue to argue with multiple people who've expressed a > real-world need for this utterly trivial request to leave the IPV6 knob > in place? A workaround for a real-world has been provided. There is no way to keep IPV6 knob's behaviour as is cause the configuration option has been removed. > In the real world I have builder machines which DO have IPv6 enabled, > which must be able to create packages that run on machines that do NOT > have IPv6 enabled. Again. It's possible to use a package built on a box with enabled IPv6 support on a box with IPv6 support disabled. -- Sergey Osokin osa@FreeBSD.org