[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Running KDE apps without kdebase (Re: Refactoring KCM
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2004-03-21 13:03:12
Message-ID: 200403211403.12828.neundorf () kde ! org
[Download RAW message or body]

On Saturday 20 March 2004 01:38, David Faure wrote:
...
> The question at heart is: should the developer of KMyApp tell his users
> "to use my app you need qt and kdelibs" or
> "to use my app you need qt, kdelibs and kdebase"
>
> If the answer depends on the distribution/packages, it becomes very messy.
>
> I think it makes sense to separate "what one needs run a KDE app"
> from "what one needs to have a KDE desktop".
> "What one needs to run a kde app" doesn't only means the libs, it means
> some binairies as well, of which kdelibs already provides quite a few,
> but khelpcenter and drkonqi are missing indeed (and kdesu if it's true
> that apps can need the kdeu binary, which I didn't know).

Yes, that's why I suggested to split kdelibs in two parts, into stuff every 
kde app needs, and things which are more optional (like kdesu or 
khelpcenter). If you have a very well integrated kde app, you'll need both, 
if you have just basic kde integration, you can get away with the "core" 
part.
Additionally splitting "kdedesktop" out of kdebase would leave kdebase quite 
small, so other basic apps could be moved there (kpdf, kmix, etc.).

Bye
Alex
-- 
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org                - http://www.kde.org
      alex@neundorf.net               - http://www.neundorf.net
[prev in list] [next in list] [prev in thread] [next in thread]