From owner-freebsd-ports@FreeBSD.ORG Wed Oct 6 17:55:14 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 808AD1065672 for ; Wed, 6 Oct 2010 17:55:14 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3F75A8FC22 for ; Wed, 6 Oct 2010 17:55:14 +0000 (UTC) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id o96HtDja082015; Wed, 6 Oct 2010 10:55:13 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.4/8.14.4/Submit) id o96HtDRC082014; Wed, 6 Oct 2010 10:55:13 -0700 (PDT) (envelope-from obrien) Date: Wed, 6 Oct 2010 10:55:13 -0700 From: "David O'Brien" To: "Andrew W. Nosenko" Message-ID: <20101006175513.GB81751@dragon.NUXI.org> References: <20100918223933.GB85995@dragon.NUXI.org> <20101002002605.GA8018@dragon.NUXI.org> <4CA844E5.7060303@infracaninophile.co.uk> <20101005183452.GF7829@dragon.NUXI.org> <20101006084040.GA53569@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 9.0-CURRENT X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? User-Agent: Mutt/1.5.16 (2007-06-09) Cc: David DEMELIER , FreeBSD Ports Subject: Re: OPTIONS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2010 17:55:14 -0000 On Wed, Oct 06, 2010 at 12:01:48PM +0300, Andrew W. Nosenko wrote: > On Wed, Oct 6, 2010 at 11:40, David O'Brien wrote: > > On Tue, Oct 05, 2010 at 11:34:52AM -0700, David O'Brien (@FreeBSD) wrote: > >> > 2010/10/3 Matthew Seaman : > >> > > In fact, you might just as well write a small HTML form, display it > >> > > using lynx or w3c or some other text mode browser[*], and then have the > >> > > form action feed into a CGI program that outputs a small Makefile with > >> > > appropriate variable definitions in it. > >> > >> I like this statement -- as it shows just how complex this will get when > >> taken to its natural conclusion. > > > > This is also how ridiculous things can get: > > > > curl 7.21.1 now offers me: > >    [X] WERROR       Treat compilation warnings as errors > > > >    Can the port maintainer really not decide if that should just be > >    turned off or turned on for FreeBSD?!? > > I wonder why -Werror even ever considered to be turned "on" at all. \AOL{me too} I mean building with "-Werror" sounds like goodness -- of course I want it. But why is the maintainer offering me a choice? What is the likelihood of the port not building with -Werror? Does he know of versions of FreeBSD where the port will not build with -Werror? Hum.. maybe I don't want -Werror. But then why didn't the the maintainer just decide we would all not build with -Werror? Given we are just building and installing Curl, what do we expect users to do choose WERROR and get a build break with -Werror? They aren't developing the next version of Curl. Can they submit a FreeBSD PR and expect the maintainer will quickly add a patch to the port to fix the warning(s)? Or will the response be "Well, don't do that."? In which case just turning off -Werror for all seems a better thing to do. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting"