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 A89421382C5 for ; Fri, 8 Jan 2021 17:07:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 21B9BE087F; Fri, 8 Jan 2021 17:07: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 D7199E086A for ; Fri, 8 Jan 2021 17:07:03 +0000 (UTC) Received: by mail-il1-f182.google.com with SMTP id t3so6824924ilh.9 for ; Fri, 08 Jan 2021 09:07:02 -0800 (PST) X-Gm-Message-State: AOAM5302QDhsEo3fVM9dEUxqU3EW510L9NdoyH/CeDlyRvmxYOGSdbeI dwV/ogehFfIxOOaDEhRPtpcY2RcPbQzyEH951gk= X-Google-Smtp-Source: ABdhPJwK0O0+1dac3XdqlGKOY/ZnOtM4wF1NWoQCSnk9SDg/6AGD4q/cVQ4xxgN8A+FSYGr4q8Rq7wSV4N4XmXaAoVc= X-Received: by 2002:a05:6e02:f93:: with SMTP id v19mr4645113ilo.154.1610125620910; Fri, 08 Jan 2021 09:07:00 -0800 (PST) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20210104013558.20072-1-whissi@gentoo.org> <091a2d35-1437-48d5-031f-6499db0a29c6@gentoo.org> In-Reply-To: From: Mike Gilbert Date: Fri, 8 Jan 2021 12:06:49 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-dev] [PATCH] acct-user.eclass: don't modify existing user by default To: Gentoo Dev Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 7bde5fc7-1151-466b-9b2a-61680d09375f X-Archives-Hash: 82969ea1ccf86db25b6b739f7c8eb2a3 On Fri, Jan 8, 2021 at 11:29 AM Thomas Deutschmann wrote: > This is a technical mailing list. Currently, acct-* stuff is breaking > stuff. Nobody has challenged this yet. > > Now I proposed a way how to unbreak stuff. > > Please tell me why we should keep broken stuff for non-technical reason > and cause harm for those who are affected? I disagree with your premise: I argue that the eclass is not "broken", and the code works as designed. You just don't like aspects of its design. If you want to change the design, you need buy-in from the maintainer, or you need to override him.