From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-63826-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 8E19013827E
	for <garchives@archives.gentoo.org>; Wed, 11 Dec 2013 02:58:19 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 5CB4CE0BCA;
	Wed, 11 Dec 2013 02:58:11 +0000 (UTC)
Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 6E6E8E0B57
	for <gentoo-dev@lists.gentoo.org>; Wed, 11 Dec 2013 02:58:05 +0000 (UTC)
Received: by mail-vc0-f177.google.com with SMTP id hq11so2066660vcb.8
        for <gentoo-dev@lists.gentoo.org>; Tue, 10 Dec 2013 18:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=sender:date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-type:content-disposition:in-reply-to
         :user-agent;
        bh=EwIY8xivd5B/3WKGiBq6JpuwfHYN9coQZavAY8u/sFY=;
        b=V8X4hy6EQi5eTcStFCBlrcrfGWymHlXYKR+p1+HiOxonmjkROrIcvWO2IIjTXnDUiR
         TiHHLHiU0CtUR/a68Jqpl+cSAqk5du2HkV9x2CjNK052nX7H03Qozbw1ILzceRnB+OT9
         +FuwsaPYzLcqC8l8C8nRwN4b5qP7R29vVYXePZm434bX6OdguObZEsDnEDvLk11Te9Iw
         9HLYwcbqmROjQUsbADiEU66g93usCUMF3Hed3KLCHPTzU+vnnoGOQWmXJ14ZwSL6IREU
         QzpI2mOa1qvUOz+pDreTyeblQd5bBRifBxPL70F+3TTxW7zeuL+Kr1M27d6ri8hf69L+
         hmEQ==
X-Received: by 10.58.44.72 with SMTP id c8mr1573378vem.37.1386730679526;
        Tue, 10 Dec 2013 18:57:59 -0800 (PST)
Received: from linux1 (cpe-76-187-91-128.tx.res.rr.com. [76.187.91.128])
        by mx.google.com with ESMTPSA id zo4sm23518363vdb.11.2013.12.10.18.57.56
        for <gentoo-dev@lists.gentoo.org>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 10 Dec 2013 18:57:58 -0800 (PST)
Sender: William Hubbs <w.d.hubbs@gmail.com>
Received: by linux1 (sSMTP sendmail emulation); Tue, 10 Dec 2013 20:57:55 -0600
Date: Tue, 10 Dec 2013 20:57:55 -0600
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up
Message-ID: <20131211025755.GA23458@linux1>
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <20131202202845.GA8574@linux1>
 <529CF973.2020008@gentoo.org>
 <529CFAA1.7080608@gentoo.org>
 <CAO-1Pb4Bspe-Yv57S70rFdeX4M48cXQ=H6D=4THfeGU9i89=Dw@mail.gmail.com>
 <20131203211130.GA31972@linux1>
 <52A2B788.3040409@gentoo.org>
 <20131208222552.GA22567@linux1>
 <52A5D89A.4080506@gentoo.org>
 <CAGfcS_ksGkU9vUSaZY=vcdposZOiZRMuVwjYBp5b=iqUGFgnFw@mail.gmail.com>
 <52A62062.9030109@gentoo.org>
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
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm"
Content-Disposition: inline
In-Reply-To: <52A62062.9030109@gentoo.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Archives-Salt: 42bfc89f-cefc-42b6-a967-76068188e5ac
X-Archives-Hash: c1bdc22e719c6e5941ee79e70e226446


--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

I think if we are going to have a default network manager in the
stages we should do it by adding a virtual/network-manager then adding
that to @system.

I couldn't find dhcpcd in @system, so I don't think it is in the
stages.

Dhcpcd by default wants to be a standalone network manager, so I also
think it is reasonable that if you want to use dhcpcd per interface
along with netifrc you should have to make sure both of them (dhcpcd and
netifrc) are in @world. You would just have to run
emerge --noreplace netifrc dhcpcd.

William


--EVF5PPMfhYS0aIcm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlKn1LMACgkQblQW9DDEZTiYEQCgrwLdXPtJ3F+VjOg/uq8xAyEs
yWYAoJaiFyJBcYX2HwA9CwXIh9m3BTi+
=XVEM
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--