organizing kdebase

[David Faure]

On Thursday 22 February 2007, Aaron J. Seigo wrote:
> On February 22, 2007, David Faure wrote:
> > On Thursday 22 February 2007, Aaron J. Seigo wrote:
> > > 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.
> 
> oh, it's not about C++. if Ruby or Python apps used these tools, that'd be 
> enough. the language used is not relevant, the kind of application is.
> 
> let's say i did an `$PACKAGE_MANAGER install kfoo`, that should pull in 
> kdelibs and kdebase/runtime. the latter should have only what is really the 
> runtime for such applications. kfoo, regardless of what language it is 
> written in, should not be using kwriteconfig.

... unless it's written in bash.

That's the point. If (or given that) we provide enough tools, you can make 
useful addons in shell scripts using kdialog, kread/writeconfig, etc.
Those scripts have runtime requirements: kdebase/runtime.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).