Another reason that gnome-core should not have a hard dependency on network manager is that nm is simply not ready for prime time. My issue with it stems from its inability to stream audio via pulse audio to another server acting as a sink over wireless without choppiness or coninuous network drop-outs. My work-around consists of renaming the S03network-manager symlinks in the /etc/rc[2-5].d directories to K03network-manager to prevent nm from even starting. Then I use WiCD to manage my connections and have experienced no network drop-outs.
As I see it, a recommends of nm, wicd, or whatever to statisfy a network dependency of gnome-core could be employed to avoid klunky work-arounds as above or removal of the gnome-core package. - Nate >> -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
