[PATCH] Silencing kbuildsycoca4

[David Faure]

On Tuesday 13 May 2008, Michael Pyne wrote:
> On Tuesday 13 May 2008, Aurélien Gâteau wrote:
> > Hi,
> >
> > I got a bit tired of kbuildsycoca4 flooding my console lately and patched a
> > few calls to kDebug() and kWarning().
> >
> > - 0001-Set-debug-zone-to-kDebug-calls.diff should be no problem I think.
> 
> I like the first patch.
> 
> > - 0002-kWarning-can-t-be-ignored-by-kdebugdialog-switch-t.diff is a bit
> > different because it replace a kWarning() with a kDebug(). Does it sound
> > ok?
> 
> Actually I've always wondered: what is this supposed to warn us (i.e. what is 
> going wrong or not as good as it could be because the mimetype is undefined?)  

Well, if the application is associated with application/rtf only, and the name
for that mimetype in KDE is text/rtf, then the application will not
be launched when clicking on a rtf file... (for this particular example an
alias was just added to shared-mime-info).

> If this is something petty I'd agree with downgrading it to debug. 

These days, where many desktop files come from outside of kde4
(e.g. kde3 files - where some mimetypes had different names,
or gnome files, or files written by ISVs/distributions),
I agree that it's not always as problematic as described above.
For instance many desktop files list all possible mimetype names they
could think of to make sure they cover those desktop differences.

But in the long run (once kde3 installations are dead and gone),
it would be nice to really have everyone standardize on shared-mime-info,
which means those warnings shouldn't trigger anymore...

So OK for debug for now, but in a few years I'll make it a kWarning again :-)

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).