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

List:       koffice-devel
Subject:    Why do we need a CVS-fresh KdeLibs to compile Koffice? (was: RE: [BUG] Cannot compile plugins/scan (
From:       Nicolas Goutte <nicog () snafu ! de>
Date:       2001-03-12 20:17:02
[Download RAW message or body]

For the second time since I know the KOffice project, the compatibility of 
KOffice to the last *stable* KdeLibs has been broken!

Personnally, I do *not* think it is good!

At first, David Faure has said in its KOffice schedule that the KOffice 
version is independant of the KDE version. De facto, this is just not true!

Secondly, it does not permit normal users that want to use the new KOffice 
to just grab the CVS version and to *test* it!

Third, it does not permit potential developpers with small computers to 
help us. They cannot just afford (time) to compile KdeLibs every then and 
when.

If you do not like what I say, then:
- make that ./configure can be called with --whitout- for the problematic 
parts. (--whiout-plugins does *not* work now!)
- call the next KOffice 2.2 or 2.3 and not 1.1.

Sorry if someone feels offenced!

-----Original Message-----
From:	Carsten Pfeiffer [SMTP:carpdjih@sp.zrz.tu-berlin.de]
Sent:	Monday, March 12, 2001 6:55 PM
To:	koffice-devel@master.kde.org
Subject:	Re: [BUG] Cannot compile plugins/scan (current CVS)

On Mon, Mar 12, 2001 at 05:40:41PM +0100, Nicolas Goutte wrote:
> scan.cpp:27: kscan.h: No such file or directory

update kdelibs/kio.

Best wishes,
Carsten Pfeiffer

_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

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