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 DB295138334 for ; Thu, 13 Sep 2018 00:23:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2013E0DD1; Thu, 13 Sep 2018 00:23:04 +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 7ED88E0DCD for ; Thu, 13 Sep 2018 00:23:04 +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 373B9335D9B for ; Thu, 13 Sep 2018 00:23:00 +0000 (UTC) Subject: Re: [gentoo-dev] acceptable alternatives to -Werror, was: Changing policy about -Werror To: gentoo-dev@lists.gentoo.org References: <20180909143221.21d784d02f51623e8c57c545@gentoo.org> <95a6e581-f005-99de-23ae-87a8e6014f1b@gentoo.org> From: =?UTF-8?Q?Ch=c3=ad-Thanh_Christopher_Nguy=e1=bb=85n?= Openpgp: preference=signencrypt Message-ID: <370e8d24-4e05-10ae-7996-b32a62afcf24@gentoo.org> Date: Thu, 13 Sep 2018 02:23:44 +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: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 2cd37086-0a64-4113-8f7b-a2e3699a448b X-Archives-Hash: cc4163271295c3398308c27cb52f2d30 Rich Freeman schrieb: >> Requirements: >> >> * Do not fail to build/install when a warning is encountered > > On a particularly critical package like a filesystem, wouldn't we want > to still fail to install when a warning is encountered? Installation will proceed, but the user will get a big fat warning that the sys-fs/zfs package is potentially broken. > I get that users might quit if packages don't install, but I'm not > sure that a filesystem corruption is going to make them any happier... If the user recognizes this as a critical package, then they can do the research before deciding on whether to use the package as is, attempt to downgrade, or wait until a fix is released. Best regards, Chí-Thanh Christopher Nguyễn