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

List:       kde-commits
Subject:    Re: branches/KDE/3.5
From:       David Faure <faure () kde ! org>
Date:       2006-09-07 15:51:02
Message-ID: 200609071751.03518.faure () kde ! org
[Download RAW message or body]

On Thursday 07 September 2006 17:39, Maks Orlovich wrote:
> > I don't understand what you mean. You mean if kdebase was compiled before
> > updating kdelibs? Well this would have given a compile error then.
> 
> Right. And some people would complain about it, but it's easy to point out 
> what they are doing wrong.
> 
> > What's better? An annoying compile error which means another
> > download+recompile, when the user was mostly updating kdebase for some
> > other reason, or a kdebase with *one* age-old rarely-happening bug still
> > being there?
> >
> > I'm surprised that this is raising objections, this technique has been used
> > for a very long time already...
> 
> Well, I spend lots of time reading kde-bugs-dist, so I much prefer something 
> not compiling to something having mystery bugs, especially fairly severe one. 
> There are way too many bugs that only the reporter can reproduce as is...

Hmm. And I have spent time updating a kde module on a machine and being annoyed
by the dependencies it required updating too. This is what I was trying to address here.

I could add a #warning but most people would ignore that.

Hmm. Oh well, I guess you're right about avoiding bug reports, I'll revert add an #error then
(more explicit than a simple compilation error).

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
[prev in list] [next in list] [prev in thread] [next in thread]