From owner-cvs-ports@FreeBSD.ORG Mon Apr 26 20:47:23 2010 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6E23106564A for ; Mon, 26 Apr 2010 20:47:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 773628FC22 for ; Mon, 26 Apr 2010 20:47:23 +0000 (UTC) Received: (qmail 24852 invoked by uid 399); 26 Apr 2010 20:47:19 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 26 Apr 2010 20:47:19 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BD5FBD5.4040904@FreeBSD.org> Date: Mon, 26 Apr 2010 13:47:17 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Sahil Tandon References: <201004242120.o3OLKYms081528@repoman.freebsd.org> <4BD38420.6000405@FreeBSD.org> <20100426052138.GA12189@magic.hamla.org> In-Reply-To: <20100426052138.GA12189@magic.hamla.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/mail/dovecot Makefile distinfo X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2010 20:47:24 -0000 On 04/25/10 22:21, Sahil Tandon wrote: > On Sat, 24 Apr 2010, Doug Barton wrote: > >> On 04/24/10 14:20, Sahil Tandon wrote: >>> Log: >>> - Update to 1.2.11 [1] >>> - Remove IPV6 from OPTIONS [2] >> >> Is that because the configure option is no longer valid? > > Indeed; configure complains that the option is unrecognized. Cool. I think this is an odd direction for the vendor to take, but thanks for answering my question. Doug >> As much as I am an IPv6 advocate, if it is possible to disable support >> for IPv6 users will still want to use that option. > > From the upstream ChangeLog: > > * configure.in: > configure: Removed --disable-ipv6 parameter. There's really no point > having it. Originally it was added back when some OSes had broken IPv6 > support, but those OSes should be long gone by now. Also we still > support automatically building without IPv6 support if it's not > detected. > -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/