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

On Sunday 07 September 2003 13:36, Tim Jansen wrote:
> But this is an issue that you can not solve by putting it into another KDE 
> module. You can only solve it by releasing the software as tarball.

Well, that would be the idea of putting it in kdeextragear -- the library will 
formally be released separately, but in practical terms it would be released 
to sync up with the KDE 3.2 release.

> Sooner or later KDE needs to get some package that has to be compiled 
> between kdelibs and application modules like kdemultimedia and kdenetworks, 
> and compiles them only 'on-demand'. Simply because the number of KDE-hosted 
> special-purpose libraries like TagLib will grow and applications will use
> them, but you can not put everything in kdelibs. 

Yes, I agree -- specifically we're starting to see a lot of projects that are 
in a similar category:  non-kde specific, but targeted towards KDE.

aRts, unsermake, mpeglib, kjs, etc. come to mind...

- -Scott

- -- 
If the answer is "more lawyers" then the question shouldn't have been asked.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/WyGMQu0ByfY5QTkRAg3qAKCVxk5BQ9qIQXpO+mUCRQorgi1PjACgkweo
dCU9vMYLHkBUJj3XxRQYuxo=
=DwQb
-----END PGP SIGNATURE-----
_______________________________________________
kde-multimedia mailing list
kde-multimedia@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-multimedia