Am 11.10.2012 02:02, schrieb Rajko:
On Wed, 10 Oct 2012 03:39:03 +0200 Marius Tomaschewski
wrote: There are no plans yet to integrate wicd, but wicked.
Does wicd need integration? Although, I asked few questions, it seems that installation and usage are not complicated and it just works.
Well... let's start from beginning. Currently there is still the NETWORKMANAGER=yes/no variable wich says whether sysconfig/ifup or NetworkManager is in use. We've to get rid of it and solve it differently as it makes problems (see Ferederic's and my mails in this thread), at least in: - to start under systemd (NM start currently shows failure in ifup mode) - to switch between NetworkManager and sysconfig We are going to: - replace NETWORKMANAGER variable with another mechanism - introduce wicked, which will obsolete sysconfig as soon as possible, that is as soons as we've teached it all the tricks. BTW: Wicked also provides a "nanny" with NM like functionality. It is not a big problem to allow WICD beeing installable and use the new mechanizm to enable itself as the "network managing service" [1]. But this is not the end of the "integration" story. With integration I mean also the initial configuration while installation / update (not just a zypper dup, but cd/dvd boot + update), the use on a virtualization host, ... And here are no plans to support / integrate WICD.
It can be included, not as a default, nor as an official option, but as a plan B, for people that have trouble with a plan A (networkmanager, ifup, wicked). It is better to have it, specially if there no other maintenance requirements than security review on a version change.
I'd say this "non official plan B" should be IMO fine, that is [1]
(+ "zypper dup" only update), when there is a bugowner/maintainer
able to fix (security) issues.
But this sounds for me like something for a maintained community
(add-on) repository, rather than regular inclusion.
Gruesse / Regards,
Marius Tomaschewski