[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#688772: gnome Depends network-manager-gnome



Since I get this to CTTE attention, I would like to stress some things.

First, I would like to strongly remember that we are all one team, Debian, and 
we should care for our users. All of them: thouse newbies who use Gnome and do 
not know nor want to know how to manually install or remove packages to the 
same degree that those sysadmins that want to cherrypick their packages one by 
one and have complicated network settings. We must work for all of them: it is 
a duty, and it is the duty we choose to do when we decided to become Debian 
members/supporters/developers/whatever you feel.

Secondly, I want to make clear why, in my *personal* experience, NM should be 
uninstallable/able to keep deinstalled from Gnome. It happens that if it is 
installed and the network is not configured by it but by hand (/e/n/i and 
ifupdown), the Gnome network-related packages like Pidgin does not work. In my 
experience, Pidgin just sits waiting for a network connection that will never 
arrive, while the computer has a perfectly working network setup. This is why 
I opted to deinstall (and knowingly overrule the Recommends) 'network-manager' 
and 'network-manager-gnome' while keeping installed the 'gnome' package.

Third, I really pray that someday NM stops being that way and be able to 
recognize existant network connections. I have not anything against NM itself, 
it is just that it does not work for me. I would even help with it if my 
programming abilities were higher that they are.

Regards

Noel Torres
er Envite
-------------------------
A: Because it breaks the logical flow of discussion.
Q: Why is top posting bad?

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: