On 2013-12-03, at 6:00 PM, William Hubbs <willi...@gentoo.org> wrote:
> On Tue, Dec 03, 2013 at 04:43:28PM -0500, Ian Stakenvicius wrote: >> On 2013-12-03, at 4:11 PM, William Hubbs <willi...@gentoo.org> wrote: >>> I would like to add a virtual/network-manager package to @system which >>> has the following rdepend settings: >>> >>> RDEPEND=" || ( >>> net-misc/netifrc >>>> =sys-apps/openrc-0.12[newnet] >>> net-misc/badvpn >>> net-misc/dhcpcd >>> net-misc/netctl >>> net-misc/NetworkManager >>> net-misc/wicd )" >>> >>> Does anyone see an issue with setting it up this way? >>> >>> William >> >> well, there is the issue where dhcpcd being installed (which is common >> for netifrc support) is going to allow netifrc to be cleaned... >> similar for NM and Wicd I expect, if those aren't in @world .... > > Please correct me if I am wrong. You can install NM or wicd and > remove netifrc and have a working system, correct? > > Dhcpcd can be run as a standalone service or per interface. In > standalone mode, the default is to automatically configure any unconfigured > interfaces it finds on your system, but this can be configured (see > dhcpcd.conf (5)). So, I'm wondering what the advantage of running dhcpcd > per interface is? > > William > I'm just referring to issues with selecting the networking stack via a virtual, is all. it'a nice that netifrc is the default due to being on top, but I expect many ppl that run netifrc use dhcp to config at least one iface, and emerging dhcpcd will then bump it out due to it now satisfying the virtual. Maybe a use flag "dhcp-only" that excludes dhcpcd from the virtual list unless set??
