From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-85888-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 786FD138239
for <garchives@archives.gentoo.org>; Mon, 10 Sep 2018 21:59:06 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 8A8EEE0E0D;
Mon, 10 Sep 2018 21:59:02 +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 34155E0DFF
for <gentoo-dev@lists.gentoo.org>; Mon, 10 Sep 2018 21:59:02 +0000 (UTC)
Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
(Authenticated sender: floppym)
by smtp.gentoo.org (Postfix) with ESMTPSA id CF2FB335D2A
for <gentoo-dev@lists.gentoo.org>; Mon, 10 Sep 2018 21:58:59 +0000 (UTC)
Received: by mail-it0-f43.google.com with SMTP id h1-v6so30816974itj.4
for <gentoo-dev@lists.gentoo.org>; Mon, 10 Sep 2018 14:58:59 -0700 (PDT)
X-Gm-Message-State: APzg51DvvtCdRiGgXpYNyxVS6149nfR59TfUaNd05Ttp+cx0Tw4FCvW5
QaKVCGBGB2NhhPxK4w4XKvyZJQ99SffaiAY/RcY=
X-Google-Smtp-Source: ANB0Vdb3gUIAdw80IiZ8ie9Co7v0S1gPk1hDSy8bQLecpOWhNe8bbh/uFfWyoah6bWcBsb0/re6BUNjKlVZh4LNTKKo=
X-Received: by 2002:a24:b701:: with SMTP id h1-v6mr20976866itf.131.1536616737739;
Mon, 10 Sep 2018 14:58:57 -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>
<1536510660.863.9.camel@gentoo.org> <ff5331b1-eb52-34eb-95f8-9b124019b809@gentoo.org>
<20180910074539.GA6512@baraddur.perfinion.com> <0d8b7f02-9c38-969c-413b-69d4dee6ca89@gentoo.org>
<CAEdQ38GfSjoKmn2jZgA-j8dxXESxe_hxu-bovSKgo6yonrR9bQ@mail.gmail.com>
<32027432-a5d2-9e63-2eac-70e62f52d242@gentoo.org> <CAJ0EP42kD8dPogU8jm9BkFsBfwW0rbyt8_gbBohCAwmcM=9uvg@mail.gmail.com>
<CAGfcS_nMxn+OwcFXVD3HATmj1sa9-_4=O7LOvis4TPir3dtYkw@mail.gmail.com>
In-Reply-To: <CAGfcS_nMxn+OwcFXVD3HATmj1sa9-_4=O7LOvis4TPir3dtYkw@mail.gmail.com>
From: Mike Gilbert <floppym@gentoo.org>
Date: Mon, 10 Sep 2018 17:58:45 -0400
X-Gmail-Original-Message-ID: <CAJ0EP40=gdNBq34CPe1goD7nnH2UppKkyh9TdocCrR=5x1so6w@mail.gmail.com>
Message-ID: <CAJ0EP40=gdNBq34CPe1goD7nnH2UppKkyh9TdocCrR=5x1so6w@mail.gmail.com>
Subject: Re: [gentoo-dev] Changing policy about -Werror
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
X-Archives-Salt: e926c44a-ca12-408d-9a14-cce4385f8849
X-Archives-Hash: 2cb3002224f55613926715d0361f8f3c
On Mon, Sep 10, 2018 at 5:31 PM Rich Freeman <rich0@gentoo.org> wrote:
>
> On Mon, Sep 10, 2018 at 5:01 PM Mike Gilbert <floppym@gentoo.org> wrote:
> >
> > On Mon, Sep 10, 2018 at 4:56 PM Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> > >
> > > On 9/10/18 10:51 PM, Matt Turner wrote:
> > > > Consider again the bug that started this. The maintainer had not built
> > > > this configuration. None of the arch teams had built this
> > > > configuration until I did for the last architecture Cc'd. The patch
> > > > committed doesn't change anything installed on the system, if not for
> > > > Werror preventing the code from building.
> > >
> > > one way to look at it though, is that it is a valuable upstream
> > > contribution that this configuration produces the error, so Gentoo is
> > > contributing to upstream development because of it.
> >
> > As an end user of Gentoo, I may not care about "contributing to
> > upstream"; I just want the software to compile and install.
> >
>
> For more critical packages (like the example of zfs) whether it
> compiles and installs isn't 1/10th as important as whether it eats my
> data...
I was clearly responding to the "contributing upstream" argument,
which has nothing to do with eating data.