[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2

Florian Hubold doktor5000 at arcor.de
Fri Aug 26 09:56:43 CEST 2011

Am 26.08.2011 09:50, schrieb Sander Lepik:
> 26.08.2011 10:27, Guillaume Rousse kirjutas:
>> I don't see where it is stated than firefox can't get updated until all 
>> extensions in the distributions work with it.
> I would call it a regression that shouldn't pass QA. One day your ads ands 
> scripts are blocked and the other day they are not. Great user experience..
>> The large advantage of packaged extensions is that they are managed by 
>> sysadmins, instead of users, which makes a difference when they are 
>> different people.
> And even larger disadvantage comes in when they are not updated. Contain 
> memory leaks and so on. The biggest problem here is that the packager who 
> imported those addons is not keeping them up-to-date.
> Sysadmin can copy those extensions into place anyway. Then it's up to him/her 
> to keep them up-to-date. Currently we have to take care of that and we don't 
> (or if anyone wants to claim that we do then we do it really poorly as there 
> are already newer versions of addons that got pushed with latest update).
> -- 
> Sander
Well, as there are mostly no bigger changes like in %files, can't an update of 
those addons
be scripted or automated halfway? So someone just needs to push this prior to a 
Firefox update?

Not saying i have an opinion pro or against packaged addons, but it is really a 
as those who do the Firefox update also need to update all those addons, which 
is unfair,
seems to me if it's not the importer/maintainer of those addons who does the 

More information about the Mageia-dev mailing list