[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Klipper
From:       Steven Sroka <sroka.steven () gmail ! com>
Date:       2011-05-17 2:07:01
Message-ID: BANLkTimwiA1K1eTmbYywLD7Dn=W4=TxPDg () mail ! gmail ! com
[Download RAW message or body]

On 16 May 2011 20:45, Sune Vuorela <nospam@vuorela.dk> wrote:
> On 2011-05-16, Steven Sroka <sroka.steven@gmail.com> wrote:
>>>On 16 May 2011 04:24, Andreas Pakulat <apaku@gmx.de> wrote:
>>> On 15.05.11 22:32:21, Steven Sroka wrote:
>>>> I'm interested if anyone knows why kdebase-workspace depends on
>>>> Klipper? I love how various KDE components are very modular, but for a
>>>> while now that weird dependency has been bugging me...
>>>
>>> Huh? klipper is part of kdebase-workspace. It does not depend on it in
>>> the sense of an external dependency.
>>>
>>> kdebase-workspace is meant to be a single module giving you a working
>>> KDE desktop, that includes a clipboard and hence klipper is part of it.
>>
>> Aha! Thanks. I should ask what else is included in kdebase-workspace?
>> (I don't need much detail)
>>
>
> ksysguard
> systemsettings
> kwin
> plasma-desktop
> plasma-netbook
> kinfocenter
> khotkeys
> kmenuedit
> freespacenotifier
> ksmserver
> cursors
> krunner
> ksplash
> kwrited
> powerdevil
> some solid plugins
> and the qt platform plugin
>
> and maybe something more.

Would it be plausilbe to have kdebase-workspace include critical
things like systemsettings, kwin, plasma-desktop, plasma-netbook,
cursors, powerdevil, etc. and have the extra things in a seperate
package? Ie. Klipper, ksysguard and so forth.

Unfortunately, what would be considered *extra* would be based on
subjective opinions.

>
> /Sune
>
>
[prev in list] [next in list] [prev in thread] [next in thread]