From owner-svn-ports-head@FreeBSD.ORG Sat May 25 02:44:25 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 6F4F8B0F; Sat, 25 May 2013 02:44:25 +0000 (UTC) Date: Sat, 25 May 2013 02:44:25 +0000 From: Alexey Dokuchaev To: Eitan Adler Subject: Re: svn commit: r318913 - in head/devel/libcfu: . files Message-ID: <20130525024425.GC89166@FreeBSD.org> References: <201305232205.r4NM5MSa002349@svn.freebsd.org> <20130524033728.GE48975@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Chris Rees , svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 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, 25 May 2013 02:44:25 -0000 On Fri, May 24, 2013 at 07:14:09PM +0200, Eitan Adler wrote: > On 24 May 2013 05:37, Alexey Dokuchaev wrote: > > On Thu, May 23, 2013 at 10:05:22PM +0000, Chris Rees wrote: > >> New Revision: 318913 > >> URL: http://svnweb.freebsd.org/changeset/ports/318913 > >> > >> Log: > >> New versions of clang complain about assigning variables to themselves. > >> > >> Let's just remove -Werror and ignore the warnings. > > > > Hmm, wouldn't it be better to fix these bugs (judging from commit log it > > should not be too hard) and send the patch upstream? > > I agree fixing these bugs is a good thing. I don't believe that this > is a function of the ports team though. IMHO disabling warnings is > the simplest, least intrusive patch that works. Good maintainer typically would work with upstream to make sure their software builds and runs on FreeBSD with little possible special tuning required. Not just it is "being nice", it also helps us to create and maintain image of an OS that is worth writing software for. :) While I agree that investing time in a large complex patch when simple workaround is available is a bit too much (unless port maintainer is also on the upstream devteam), fixing *simple* things such as compiler warnings is better than throwing -Werror. ./danfe