From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-85908-garchives=archives.gentoo.org@lists.gentoo.org>
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 B41C4138334
for <garchives@archives.gentoo.org>; Thu, 13 Sep 2018 00:35:02 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id B730AE0DD8;
Thu, 13 Sep 2018 00:34:58 +0000 (UTC)
Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172])
(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 5E63AE0DD0
for <gentoo-dev@lists.gentoo.org>; Thu, 13 Sep 2018 00:34:58 +0000 (UTC)
Received: by mail-pl1-f172.google.com with SMTP id f1-v6so1767801plt.4
for <gentoo-dev@lists.gentoo.org>; Wed, 12 Sep 2018 17:34:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:content-transfer-encoding;
bh=g3zVC6bbDo2AeHFcATnmM9iuZX1ubwWrtv+gZM74TEo=;
b=miRX8EVRF60eWSWGsBV5AvnEgn/sFYs1/J75Bui06EGQl8kA2q9GwoKlfr/WCjybVj
icROJCQKl2PmHfSvuKSbpiy9LTE89W6Osmg9NNdcAsObNeN30wV7nYw/hN/wHvzO5FR1
MaatJGij3maQhk4ueluiJznETm6WVSd6Y9oTDUeR04nASsigNeAmAmBVA7nrGoVXXmi7
Ipl2YPOPSVIrfU5e9ndeXP9xuqzlLpFILkRUm/coBS39PyLCi2JB+ILW+cxvyTqOpGw4
okre6+wCS91tjpd0l1Q9URXxo0x4smom3tvKoFJpVmw72sD2Uurv5gqp6LVs2hqSTVwz
dfIQ==
X-Gm-Message-State: APzg51BPFGCITqh4Wqcq2TYRAidOfqVrJGPVwaW4MF8dfOOYJHNu81Kj
urpWyAcECmOWC6ydJiE8voJah28bhZ4jRT25E/6uGMzt
X-Google-Smtp-Source: ANB0VdYgLVb7aYaacpx7PHTufDVnZ9RHReIZUxfl2mfCOgQp5Qwp9XaPDXijTgPDG8TfDQnjg2k/w6mZu16D5iINXGQ=
X-Received: by 2002:a17:902:a613:: with SMTP id u19-v6mr4775692plq.234.1536798896961;
Wed, 12 Sep 2018 17:34:56 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
References: <20180909143221.21d784d02f51623e8c57c545@gentoo.org>
<95a6e581-f005-99de-23ae-87a8e6014f1b@gentoo.org> <CAGfcS_=-v=8zDjWfGm=h1vTdHi1T82PCGey16DWa3HWcyVM0Bw@mail.gmail.com>
<370e8d24-4e05-10ae-7996-b32a62afcf24@gentoo.org>
In-Reply-To: <370e8d24-4e05-10ae-7996-b32a62afcf24@gentoo.org>
From: Rich Freeman <rich0@gentoo.org>
Date: Wed, 12 Sep 2018 20:34:45 -0400
Message-ID: <CAGfcS_m5TrR5Jtx0kTHuTkiGbntaJiJ=9bWHtdQCPefO4BEeSA@mail.gmail.com>
Subject: Re: [gentoo-dev] acceptable alternatives to -Werror, was: Changing
policy about -Werror
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 337573a4-2212-42bd-8663-eca479297525
X-Archives-Hash: 7e5f1471cbf30a3a8b7064d9a5ac74bb
On Wed, Sep 12, 2018 at 8:23 PM Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n
<chithanh@gentoo.org> wrote:
>
> 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 t=
he
> 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.
But, you've ALREADY overwritten the previous version of the package
that presumably didn't have this problem. What if downgrading doesn't
cause the problem to go away? What if it is due to some dependency or
toolchain change? Users would presumably want to roll back to the
binaries that were working just a few minutes ago, not build new ones
that might or might not have the same issue.
--=20
Rich