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

List:       kopete-devel
Subject:    Re: [Kopete-devel] Kopete does not compile
From:       Olivier Goffart <ogoffart () tiscalinet ! be>
Date:       2003-08-29 20:45:03
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Le Vendredi 29 Août 2003 22:05, Martijn Klingens a écrit :
> On Friday 29 August 2003 21:25, Olivier Goffart wrote:
> > this time, the bug is in configure. it does not seems detect that it need
> > to compile .
>
> What does it say? Is it my configure check or something else in the generic
> kdenetwork code?

here is a part of the ./configure output

checking knotifydialog.h usability... yes
checking knotifydialog.h presence... yes
checking for knotifydialog.h... yes
checking for kdelibs newer than 3.1.x... checking for xml2-config... 
/usr/bin/xml2-config


And the code in compat is not compiled (if i add errors here , it does not 
complain)

>
> Does it work if you replace admin/ in kdenetwork with KDE_3_1_BRANCH?

no

> > Martijn, don't you think we should drop kde 3.1 support?
>
> No. 3.2 is waaaaay too bleeding edge to depend upon for our users. And the
> release is still a while away. I wouldn't be surprised if we can release 
> an 0.8 before 3.2 even...

realy?
that's true that more than 4 month is big. but look in the past:
the time between kopete 0.6 and 0.7: february-august= 6 month
between 0.5 and 0.6:  4 month   (and wa was about to release 0.5.1 insteads)
and between 0.4.1 et 0.5: 4 month.

so we are followinf a normal release cycle.
I'll add that the kde release impose us a feature freezee, so there will be no 
features between 0.8 and 1.0 ?

if we release something, it could be Kopete1.0-beta
(we could release a separate dist for kde 3.1)


> > KDE Head will even drop qt 3.1 support on monday.
>
> True, but by maintaining an old KDE_3_1_BRANCH admin/ dir you can probably
> continue working on it.
>
> > I don't have enough diskspace left on my HD to recompile it, and last
> > time i tried it, KDE was verry unstable (i compiled only kdelibs, not
> > others (just kcontrol because it's not binary compatible) )
>
> I suggest installing KDE HEAD to a separate dir and build kopete against
> that. Perhaps also kdebase. The rest can then run against the old libs
> because they are not replaced. That's what I do at home.
>
> > Anyway, after monday (which is the day of the planed features frezee) i
> > would still like to code what i planed to do in the TODO file in kopete.
> > i don't know if we should put that somewere.. i guess the "include all
> > basic features necessary for a 1.0 release" in the kde feature include
> > theses.
>
> 1. I do _NOT_ want to call the next release 1.0. No way on earth we're
> going to hit BC in time.
>
> 2. Your list of TODO items is quite big and intrusive. The planned features
> list is not meant to be a 'let's add everything here so we can basically
> continue coding as if there were no feature freeze' list. Please pick only
> a couple of items and try to work on stability and bug fixing in some 6
> weeks or so instead of adding features after that.

[Attachment #5 (application/pgp-signature)]

_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel


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