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

List:       kde-devel
Subject:    Re: cleaning up kdesupport for KDE 1(.1).2, KDE 2.0
From:       Lars Knoll <knoll () mpi-hd ! mpg ! de>
Date:       1999-07-12 20:25:00
[Download RAW message or body]

On Mon, 12 Jul 1999, John Corey wrote:
>pbrown@redhat.com wrote:
>> 
>> I move that we clean a few libraries out of kdesupport for the next
>> releases of KDE.  Namely:
>> 
>> gdbm - this is a GPL library that cannot be used at all for commercial
>> application development, and I don't think any KDE applications are using
>> it.  If there is even just 1 application using it, it should distribute it
>> by itself, rather than encouraging its use.
>
>The GPL's a fine license, I don't see why we should banish GPL libs. 
>After all, kdesupport is just support libs, not part of KDE itself. 
>Commercial developers are free to use/not use these.  If it isn't used,
>sure go ahead and axe it.

Because non GPL'ed programs are not allowed to link to it, and (AFAIK) no KDE
program uses it. Why should we keep stuff no KDE app uses?

>> jpeglib6a - is this still needed? If so, by what?
>> 
>> js - is this javascript library used / will it be used?  I know it isn't
>> right now, and there may be a better implementation anyway.
>
>I tried configuring with this recently, it gave a warning suggesting you
>use another js library.  So, perhaps we either put that other one in? 
>Configure pointed to something like www.ngs.fi if I recall correctly,
>but at the time that wasn't resolving...

The version of the js lib in kdesupport is not the newest one. Anyway, I still
hope we will have some jscript support some time in the future. For that, we
will need libjs, since it's the only free jscript library I know of (if we
don't want to write our own implementation... ;-). So I wouldn't remove it
completely, but perhaps one could disable compilation for the moment.

Cheers,
Lars

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