Re: Blacklisting themes?

["Mathias Hasselmann" <Mathias Hasselmann gmx de>]

> 1. User gets a crash in gnumeric-n.m, reports it.
> 
> 2. Developer determines that the crash is in the theme engine.
> 
> 3. Developer blacklists the theme engine; releases gnumeric-n.m+1
> 
> 4. User updates gnumeric, and can't run it anymore because it barfs on
> that engine.  He still risks crashes in other apps.
> 
> I don't think blacklisting will work due to (4).  If you require the
> user to upgrade the app, then the user may as well update the theme
> engine, too.
> 
> It's better to tell the user "you should really update your theme
> engine"; that will fix his problem and prevent crashes in other apps as
> well.

Well, but that still keeps the problem of countless dups in Bugzilla and bad reputation. I support the idea of blacklisting as this could be some efficient measure for quality control, but only if the blacklisting doesn't happen in the application, but in GTK+. Blacklisted themes would by detected by the MD5, SHA256, whatever hash over their gtkrc. Distributors would be encouraged to frequently backport our blacklist into their current  GTK+ package. The blacklist even could be packaged separatly to make upgrades cheap.

Just my 2 cents...

Ciao,
Mathias
-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser