From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 51707138334 for ; Sun, 9 Sep 2018 23:46:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 98E9FE0B1C; Sun, 9 Sep 2018 23:46:12 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 48D0FE0B15 for ; Sun, 9 Sep 2018 23:46:12 +0000 (UTC) Received: from [192.168.2.102] (dslb-002-200-185-218.002.200.pools.vodafone-ip.de [2.200.185.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: chithanh) by smtp.gentoo.org (Postfix) with ESMTPSA id D1CCD340F16 for ; Sun, 9 Sep 2018 23:46:10 +0000 (UTC) Subject: Re: [gentoo-dev] Changing policy about -Werror To: gentoo-dev@lists.gentoo.org References: <20180909143221.21d784d02f51623e8c57c545@gentoo.org> <1536510660.863.9.camel@gentoo.org> From: =?UTF-8?Q?Ch=c3=ad-Thanh_Christopher_Nguy=e1=bb=85n?= Openpgp: preference=signencrypt Message-ID: Date: Mon, 10 Sep 2018 01:46:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.9.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <1536510660.863.9.camel@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 58fad335-5eb3-4d8b-8aee-7dc3b3dbeb99 X-Archives-Hash: 18660c8203351c034e7c08a3515f443b Michał Górny schrieb: > Are you suggesting that > upstream is going to detect all those situations and prevent them from > occurring, or are you going to WONTFIX the resulting bugs? No. With -Werror, upstream indicates that if a warning occurs, the build should fail and the resulting code not be installed on user systems. Instead, someone knowledgeable should look at the situation *first* and determine whether it is a bogus warning, a trivial issue, or something which warrants further attention. I have long disagreed with QA policy on this, and think that ebuilds should respect upstream here. Of course giving users the ability to override. Best regards, Chí-Thanh Christopher Nguyễn