vivid package manager

[Harald Sitter]

On Fri, Jan 23, 2015 at 5:09 PM, Glenn Holmer <shadowm at lyonlabs.org> wrote:
> On 01/23/2015 09:57 AM, Harald Sitter wrote:
>> On Fri, Jan 23, 2015 at 4:46 PM, Glenn Holmer <shadowm at lyonlabs.org> wrote:
>>> Please consider installing Muon Package Manager by default in order to
>>> provide something more substantial than Muon Discover.
>>
>> what are use cases that would indicate muon being a better fit than
>> muon-discover?
>
> It's a question of choice. I'm not suggesting that Package Manager
> replace Discover, but that it be installed alongside it by default. Some
> users prefer the level of detail provided by Package Manager.

There is a long standing policy against shipping two applications of
the same kind on the ISO. It's why we have kate instead of kate and
kwrite. Firefox instead of firefox and rekonq. Amarok instead of
amarok and juk etc. etc.

Now don't get me wrong, we are very aware that muon-discover doesn't
cut it for everyone. It is, after all, a software center and not a
package manager. In fact when we originally made the call to use a
software center instead of the muon package manger (back then that
software center was muon-installer) we had discussed this quite a bit
and reached the conclusion that someone who would wish to have the
advanced feature set of muon package manager is also knowledgeable
enough to discover (pun intended) the availability of such an option
and install it. So, if you will, muon-discover is the gateway to muon
;)

All that being said, if you have something specific that you think
should be supported in muon-discover, I'd encourage you to start a
discussion for example in the KDE Visual Design Group forum [1] or the
KDE Brainstorm forum [2].

[1] https://forum.kde.org/viewforum.php?f=285
[2] https://forum.kde.org/viewforum.php?f=83

HS