[Pkg-utopia-maintainers] Bug#500119: Bug#500119: Better way to avoid both knetworkmanager and nm-applet are started in parallel

Otavio Salvador otavio at debian.org
Tue Nov 25 11:37:21 UTC 2008


PCMan <pcman.tw at gmail.com> writes:

> If you don't install nm and nm-applet, it doesn't matter what's inside
> nm-applet.desktop.
> Fixing the incorrect desktop file won't break any existing things and
> has no relationship with your question. If a user don't want the
> dependencies brought by nm, he/she shouldn't get it installed.
> Besides, the reason why nm has so many dependencies is understandable.
> To get your Linux desktop correctly connected to the internet is very
> difficult and can be very complicated. That's why nm is so
> complicated. So personally I think nm is still an acceptable option
> even for lightweight desktops since it works quite well.
> Some might argue that wicd can do this well and it's small, too.
> However, it's written in python, and that "small" program need python
> and its libs, which are not thin at all.
> Network manager is still a reasonable and sensible option if you need
> to manage your connections with GUI.

The .desktop change of nm-applet I'm ok with. And this is really
recommended to be done to allow it to be used by other compatible desktops.

> The point is, whether the installer for lxde flavor includes nm or
> not, it'll never works for the users even when they really want to use
> it and install nm manually. That's why this fix is definitely needed.

Agree.

But install it in tasksel is a completely different history.

> On Tue, Nov 25, 2008 at 7:33 AM, Otavio Salvador <otavio at debian.org> wrote:
>> Adeodato Simó <dato at net.com.org.es> writes:
>>
>>> * Andrew Lee [Sat, 15 Nov 2008 16:11:18 +0800]:
>>>
>>>> Cc'ed this to debian-boot and debian-release.
>>>
>>>> Dear RMs,
>>>
>>>> This is only one line change in nm-applet.desktop which benefit other
>>>> Window Managers and Desktops user. Please accept this change into Lenny.
>>>
>>> Has somebody verified that the change ensures it doesn't get started in
>>> KDE, just as with OnlyShownIn=GNOME? Or do you have first-hand knowledge
>>> of that? In any of those case, I'm ok with that one change.
>>
>> This is somewhat complicate to decide. I see two sides in this
>> question:
>>
>>  1) adding Network Manager for LXDE we'll give a more ready to use
>>  desktop for laptop users and give some extra bonus for regular users;
>>
>>  2) LXDE seems to fit very well with users wanting a low-resource
>>  environment and Network Manager is not thin (it bring a lot of
>>  libraries and consumes resources);
>>
>> So personally I'm unsure which is the best option.
>>
>> From my POV I believe we shouldn't add Network Manager on lxde-desktop
>> task since it's quite easy to do it and we can make the installation
>> fat for a user that is limited regarting space, memory and cpu power.
>>
>> What others think about it?
>>
>> --
>>        O T A V I O    S A L V A D O R
>> ---------------------------------------------
>>  E-mail: otavio at debian.org      UIN: 5906116
>>  GNU/Linux User: 239058     GPG ID: 49A5F855
>>  Home Page: http://otavio.ossystems.com.br
>> ---------------------------------------------
>> "Microsoft sells you Windows ... Linux gives
>>  you the whole house."
>>
>

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio at debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."





More information about the Pkg-utopia-maintainers mailing list