--nextPart2423860.gdoJdV8cDf
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On February 22, 2007, David Faure wrote:
> > apps
> > =3D=3D=3D
> > [...]
> > libs:
> > libkonq/ (file management goodies and guffaws)
>
> "belly laughs"? ;)
> Well libkonq is an issue in itself since it's used by kicker in a few
> places right now (for KonqBookmarkManager and KonqOperations::doDrop) but
> I'll be working on moving doDrop to kio, it seems to be widely needed.

ok, i'll hold off on moving libkonq for the time being until we see what=20
becomes of it.

> > utils
> > =3D=3D=3D
>
> I'm not convinced about the need to separate utils from runtime.
> The reason is: most of those could actually be runtime requirements of 3rd
> party apps or scripts. Just like you left kcheckpass in runtime, 3rd party
> apps and scripts need: kdialog, kioclient, kreadconfig, kstart...

scripts, yes. apps? i dunno... here's how i determined things:

=2D is there an API equivalent, making the application unnecessary to call?
=2D do applications call it (i'd check box lxr.kde.org and in some cases=20
google's code search)?

i didn't count scripts (unless they are shipped as part of the desktop, i=20
suppose?) as valid requirements for putting something into runtime. users a=
nd=20
admins writing scripts to automate things can rely on kdebase being=20
installed.

my thoughts are that runtime should be exactly that: the collection of=20
applications we know that software relies on. this implies a larger burden =
of=20
portability and maintenance in my mind.

> > kappfinder (find legacy apps and add them to your menu; maybe this moves
> > out of base altogether?)
>
> Yeah - nothing runs kappfinder automatically, right?

not that i could find, no. any thoughts on where to put it? kdeutils? i don=
't=20
want that to become a dumping ground either though...

> > kdebugdialog (set actions to take for output from the various debug
> > areas)
>
> OK, that one fits with your definition of utils; but it's the only one :-)
>
> > 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)
>
> Those are all possible (and likely) runtime dependencies of many scripts.

yes, particularly kdialog, kreadconfig and kwriteconfig. the latter is used=
 in=20
an "more easily install amarok from svn" script for developers in the amaro=
k=20
source distribution, for instance, and i know admins who use those in their=
=20
scripts extensively as well.

however, i didn't consider scripts a reason to put something into runtime/,=
=20
which i kept specifically for application software (which can be written in=
=20
python, ruby, etc.. but that's not a "script" in my mind). scripts can depe=
nd=20
on kdebase/?

> > kinstalltheme (install time pixmap cache creator; may be obsoleted befo=
re
> > 4.0)
>
> Runtime dependency of themes?

hm ... yes, this probably is runtime/ material ... will shift it over there.

> > solidshell (command line utility for interacting with hardware via soli=
d)
>
> Not sure if it is meant to be used by scripts or advanced users or just f=
or
> debugging.

as kevin said, it could be used for any or all of that.

> Also, kutils vs kdeutils vs kdebase/utils gets confusing ;)

we just really like that word. =3D)

=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)

--nextPart2423860.gdoJdV8cDf
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBF3chE1rcusafx20MRAh0CAJ0WlcwziYwIQn03Cg54r2cs49DJIQCfRxfy
uUX6UEzchmTUUToG9nn0Phg=
=+2dq
-----END PGP SIGNATURE-----

--nextPart2423860.gdoJdV8cDf--