> > Not at all. kde-apps scripts might use kstart to start something a certain
> > way; that's a runtime dependency for scripts that users will launch, like
> > e.g. kdialog. Same for kreadconfig: it's meant for scripts to use.
>
> and this is precisely why i put them together in another directory: they
> aren't user apps, they aren't workspace and they aren't dependencies for
> application software (runtime/)
>
> i'd like to see us keep runtime/ specifically as the set of dependencies that
> one could expect to see required in a package manager when installing a kde
> application. kreadconfig doesn't strike me as fitting that criterion at all
> since application software doesn't use kreadconfig (they use KConfig)

I think the issue here is more that non-KDE applications that use
these tools to integrate into KDE should be able to depend on them to
be present.

Rich.