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

List:       kde-core-devel
Subject:    Re: organizing kdebase
From:       Oswald Buddenhagen <ossi () kde ! org>
Date:       2007-02-22 9:13:01
Message-ID: 20070222091301.GA4569 () ugly ! local
[Download RAW message or body]

On Wed, Feb 21, 2007 at 03:17:27PM -0700, Aaron J. Seigo wrote:
> workspace
> =======
> 
> libs:
> kdmlib -> kdm/lib, greeter classes
>
i don't like this idea - otherwise i had done it in the first place. ;)
the greeter plugins are needed by both kdm and kdesktop_lock (whatever
it becomes now). putting it under kdm/ makes compiling it without kdm
much harder. but i wouldn't be opposed to renaming the dir once dmlib
moves into workspace/lib/ (or whatever it was).

> utils
> ===
> kdialog (bring your scripts to life with kdialog[tm])
> kioclient (kio ops that were previously in kfmclient)
> kquitapp (quit an application via IPC)
> kreadconfig (read and write kconfig entries via the command line)
> kstart  (handy utility to start applications in various states)
> solidshell (command line utility for interacting with hardware via solid)
> 
these are really backend tools usually used from scripts, some of them
critical to workspace. lumping them together with "pure 'user' tools" like
kdebugdialog just does not feel right. they are more like runtime/utils/
or something.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
[prev in list] [next in list] [prev in thread] [next in thread]