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 C0DE81396D0 for ; Thu, 24 Aug 2017 15:22:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 648ED1FC042; Thu, 24 Aug 2017 15:22:35 +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 193F0E0C75 for ; Thu, 24 Aug 2017 15:22:35 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id F253334185F for ; Thu, 24 Aug 2017 15:22:33 +0000 (UTC) Subject: Re: [gentoo-dev] Guidelines for dangerous USE flags To: gentoo-dev@lists.gentoo.org References: <17347fd7-d6ed-4c08-8d02-24df9237b576@gentoo.org> From: Michael Orlitzky Message-ID: <7f59fb4d-e7a2-3bd1-9274-de0bc94affb8@gentoo.org> Date: Thu, 24 Aug 2017 11:22:24 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 7725b347-96f8-4864-820a-e5ff8ad1c6ac X-Archives-Hash: 925a258fc73f7b15c2d6386e0b685883 On 08/22/2017 02:44 PM, Robin H. Johnson wrote: > From a Gentoo Infrastructure team perspective, we'd strongly prefer USE > flags, because that fits better into existing configuration management > tools, almost none of which have handling for EXTRA_ECONF or rebuilding > after EXTRA_ECONF changes (rebuild-on-USE-change is supported). > > And please do bring that option back, we do use it for NRPE in a limited > set of cases (eg to avoid hard-coding passwords into the NRPE config). > It's back, but the flag is masked. Since the USE flag mask is going to retroactively hit people who use --newuse, I suggest adding net-analyzer/nrpe -command-args to your /etc/portage/profile/package.use.mask right now, to avoid surprises.