From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9D7B313827E for ; Sat, 14 Dec 2013 05:56:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 45EDBE0C04; Sat, 14 Dec 2013 05:56:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5C381E0A85 for ; Sat, 14 Dec 2013 05:56:34 +0000 (UTC) Received: by smtp.gentoo.org (Postfix, from userid 2127) id AA80F33F3BA; Sat, 14 Dec 2013 05:56:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 9FAA933F2A1 for ; Sat, 14 Dec 2013 05:56:33 +0000 (UTC) Date: Sat, 14 Dec 2013 05:56:33 +0000 (UTC) From: "Jorge Manuel B. S. Vicetto" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up In-Reply-To: <20131211025755.GA23458@linux1> Message-ID: References: <20131202202845.GA8574@linux1> <529CF973.2020008@gentoo.org> <529CFAA1.7080608@gentoo.org> <20131203211130.GA31972@linux1> <52A2B788.3040409@gentoo.org> <20131208222552.GA22567@linux1> <52A5D89A.4080506@gentoo.org> <52A62062.9030109@gentoo.org> <20131211025755.GA23458@linux1> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) 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 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archives-Salt: ea2d55af-32a0-4a72-9530-fece91312a21 X-Archives-Hash: 674920066a87b26938cb0dcba890e994 On Tue, 10 Dec 2013, William Hubbs wrote: > My issue with what we are currently doing is not whether we have a > default network provider in the stages or not, but it is just that the > netifrc use flag on OpenRC is bogus. OpenRC doesn't need netifrc for any > reason. William, the "push" for the use flag was to ensure that users would keep the existing networking functionaility and more importantly their network configuration. Without it, portage would "happily" clean /etc/conf.d/net - something not desirable by most.