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

[Maarten Vanraes]

Op vrijdag 26 augustus 2011 09:56:43 schreef Florian Hubold:
> 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).
> 
> 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 nuisance
> 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 update.

well, regardless of what we do, we should update all the packages requiring 
any package to be sure they are working/updated, before the actual push from 
testing to updates, imho.

in fact, i think updates should be blocked from pushing until all packages 
dependant on it or also working or updated for it. perhaps if such an addon 
package is badly maintained, it should be dropped; if not, perhaps the move 
from testing to updates can wait one more day...?

one could argue that if it's a security fix, it should not have to wait, but 
then one could argue that certain plugins increase security and thus those 
should definately be working before the move from testing to updates. so i 
guess i would call this "maintainers privilege". none the less, if this is 
chosen, the others should follow quickly or maybe they aren't maintained well, 
so they could be dropped.

for cauldron, there is no such need.