On Sat, Dec 14, 2013 at 08:47:01PM +0000, Jorge Manuel B. S. Vicetto wrote: > OK, I see what you mean. > To be clear, I'm not ready to have a stage3 without netifrc. If / when we > update catalyst so that the new stage3 is the sum of @system and > additional packages, we can move netifrc to that list.
Actually I'm not even sure how necessary that kind of update is. I didn't quite follow what the reasoning against my second proposal was. Once openrc-0.12.4 is stable everywhere it is going to go stable, I want to add virtual/network-manager to the tree. This would contain a list of network manager providers. I think adding it to the tree is good, because we have other virtuals for multiple packages that perform the same function -- virtual/logger, virtual/mta, etc. Once that is done, we could easily add it to @system then I would drop the netifrc use flag. That would take care of the situation if netifrc was the default provider. Then, if you decide to add the function you are talking about to catalyst, we could look into dropping virtual/network-manager from @system. I'll attach the ebuild below so everyone sees it. William
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
EAPI=5
DESCRIPTION="virtual for network managers"
HOMEPAGE=""
SRC_URI=""
LICENSE=""
SLOT="0"
KEYWORDS="~x86"
IUSE=""
DEPEND=""
RDEPEND=" || (
net-misc/netifrc
>=sys-apps/openrc-0.12[newnet]
<sys-apps/openrc-0.12
net-misc/badvpn
net-misc/connman
net-misc/dhcpcd
net-misc/netctl
net-misc/NetworkManager
net-misc/wicd
)"
signature.asc
Description: Digital signature
