From kde-core-devel Thu Feb 22 16:25:33 2007 From: "Aaron J. Seigo" Date: Thu, 22 Feb 2007 16:25:33 +0000 To: kde-core-devel Subject: Re: organizing kdebase Message-Id: <200702220925.38236.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=117216154025584 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart3342882.VqI8DTjEuY" --nextPart3342882.VqI8DTjEuY Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On February 22, 2007, Oswald Buddenhagen wrote: > On Wed, Feb 21, 2007 at 03:17:27PM -0700, Aaron J. Seigo wrote: > > workspace > > =3D=3D=3D=3D=3D=3D=3D > > > > 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.=20 really? just do what i did with plasma/lib: put it in=20 workspace/CMakeLists.txt. voila! > but i wouldn't be opposed to renaming the dir once dmlib=20 > moves into workspace/lib/ (or whatever it was). ok, so we will at least call it libkdm to keep it consistent. we'll still h= ave=20 to see about moving it into kdm/lib ... > > utils > > =3D=3D=3D > > 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 soli= d) > > these are really backend tools usually used from scripts, some of them > critical to workspace. which are critical to workspace? and by 'critical' i mean: applications wil= l=20 start to function poorly, not 'but we are really used to having them there= =20 and some user depend on them for day to day work'. the latter is why they a= re=20 in kdebase. > lumping them together with "pure 'user' tools" like=20 > kdebugdialog just does not feel right. they are more like runtime/utils/ > or something. what applications use them? according to my research: none. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 =46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com) --nextPart3342882.VqI8DTjEuY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBF3cQC1rcusafx20MRAjhNAJ9o+IQVOsgb3HQrSABDdfh/424VNgCginTn 82Kp7iST0bdHL4kpEUc97UU= =O71M -----END PGP SIGNATURE----- --nextPart3342882.VqI8DTjEuY--