aKregator in CVS

Frank Osterfeld frank.osterfeld at gmx.de
Wed Dec 8 00:33:25 GMT 2004


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

On Tuesday 07 December 2004 22:47, Allan Sandfeld Jensen wrote:
> On Tuesday 07 December 2004 22:35, George Staikos wrote:
> >    Moving it into kdepim was suggested because of the nature of
> > integrating such things in Kontact.  This apparently wasn't too well
> > accepted, so we have to split it up across various modules.  Then again,
> > librss dependency could make kdenetwork better.  I propose:
> > application: in kdenetwork
> > konq plugin: in kdenetwork or kdeaddons
> > kontact plugin: in kdepim
> > librss: in kdenetwork
>
> Doesn't the kontact and konq plugins both have to be in kdeaddons because
> of the dependency?

The Kontact plugin doesn't depend on akregator at build-time; it could go to 
kdepim like the weather and the newsticker plugins, which also require apps 
not included in kdepim at run-time but don't have any build-time dependency.
Akregator would be available in Kontact after installation of kdenetwork, no 
matter in which order the modules were compiled.

The Konqueror Plugin depends on kdebase. I don't know the policy here, maybe 
that makes it necessary to put it into kdeaddons?

Regards,

Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBtkvbFZrnbFOwfvQRAvB9AJ0XAIllKZQBRYgbHvM2QfuPval/IgCgmjGP
YbRMj5LDQuNx8S9D+VuVNl0=
=LsN1
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list