Le 09/10/2012 01:52, Rajko a écrit :
On Mon, 08 Oct 2012 17:24:33 +0200 denisart benjamin1
wrote: I think a branding should be created for a better integretion with environment. Branding is the smallest issue.
An entry in Yast for choose the network manager could be a great thing YaST is based on ycp language that only few people know and they are busy. That means only third party developer can make such addition, but as one has to learn ycp first, it is not likely that will happen.
or, better simply using our own GUI interface for wicd daemon. That is actually the only viable way.
Basicaly, a few of users use already the package on network:utilities, just purpose the package could be a start. What people have to do to have wicd running? Do you have some example configuration? What works under wicd, and what not? Is YaST aware of network configured with wicd? If firewall working?
Wicd could already supports ipv6 (http://aur.archlinux.org/packages.php?ID=46750) Unfortunately, I don't find any topics whose speaks of advantages of wicd on any others networkmanager. About article from bootstrapping-awesome.org, that makes me say there is real interests to integrate wicd into OpenSuse. Article is talking about "something" that should help in the future, maybe even wicd.
But the simple fact that a numerous users use this one would be an argument.
A lot of users have opened a topic on opensuse forum. Wicd works without any tipcs or tricks, just install package and an applet is loaded of notifications area. Wicd is lite and a this step, it doesn't support vpn connections but it is the only problem. The daemon works as a backend, I imagine yast could be aware of network with wicd because it used already and robusts tools to establish network connection : wireless-tools, wpa_supplicant,... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org