On Sat, 14 Dec 2013, William Hubbs wrote:
On Sat, Dec 14, 2013 at 05:56:33AM +0000, Jorge Manuel B. S. Vicetto wrote:
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.
Hi Jorge,
Portage will not clean /etc/conf.d/net, and this is not related to the
use flag. That is handled by the block starting at line 212 in
openrc-0.12.4.ebuild. I had to modify the file so portage
wouldn't remove it.
Ah, that's good to know.
I mentioned /etc/conf.d/net as you know I lost it on a production box when
the new openrc with netifrc was initially released. It's good to know that
was fixed on a different way.
The push for the use flag was because people didn't think it was enough
for me to put out a news item telling them that they should emerge
netifrc if they wanted to continue using it once this version of OpenRC
was installed.
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.
William
Jorge
