Running KDE apps without kdebase (Re: Refactoring KCM technology)

Waldo Bastian bastian at kde.org
Sun Mar 21 14:49:36 GMT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun March 21 2004 15:20, Rob Kaper wrote:
> On Sun, Mar 21, 2004 at 02:03:12PM +0100, Alexander Neundorf wrote:
> > > I think it makes sense to separate "what one needs run a KDE app"
> > > from "what one needs to have a KDE desktop".
> >
> > 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.
>
> Why optimize KDE to benefit those who don't fully integrate with it?

Yes, I don't see that either. The distinction between "what one needs run a 
KDE app" and "what one needs to have a KDE desktop" is a useful one though.

Alex suggests a distinction between "compile time dependency" and "runtime 
dependency" but I don't see a strong need to differentiate those two and the 
argument that "if you have just basic kde integration, you can get away with 
the "core" part." is a good argument _against_ it IMHO, because it 
effectively encourages third party developers to not fully integrate.

Cheers,
Waldo
- -- 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
^ bastian at kde.org | Is your software SUSE LINUX READY? | bastian at suse.com
^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAXauAN4pvrENfboIRAhRaAJ9h/izBzh5w6jLjWZb4IVx8uC5FlQCaA0KG
5ZG/LILsdMSzUc4WO2/4aQs=
=RauW
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list