organizing kdebase
David Faure
faure at kde.org
Thu Feb 22 17:58:53 GMT 2007
On Thursday 22 February 2007, Aaron J. Seigo wrote:
> On February 22, 2007, Richard Moore wrote:
> > 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.
>
> that's why they are in kdebase, and not in kdebase/apps or kdebase/workspace.
>
> perhaps "tools" is a better word than "utils" here then; "utils" seems to
> imply "miscelaneous crud" which isn't true. nor was that my intention with
> this grouping.
>
> keeping runtime/ to mean "those applications which form the runtime
> requirements of KDE applications" seems to be a good separate goal to me for
> reasons i've already stated.
I don't see why we need to separate the runtime-requirements of C++ KDE applications
from the runtime-requirements of KDE-related scripts. Especially since we're arguing
over 6 small tools :)
--
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel
mailing list