On Fri, Nov 17, 2017 at 2:01 PM, Benjamin Kreuter <ben.kreuter@xxxxxxxxx> wrote:
Again, why allow addons to be packaged at all if we are not prepared to
block browser updates that break addons?
I don't believe we should be in the business of determining which applications are
worthy of packaging... if someone wants to do the work, more power to them.
Alternatively, rather than block the updates, at least leave the last
working version in the repository so that users can downgrade to
something more recent. Right now it looks like F26 users can either
accept Firefox 57 and live without their addons, or downgrade to 54;
why not continue making 56 available for users who want it? As far as
I know DNF is capable of handling such scenarios, although maybe there
are other parts of the infrastructure that make this difficult.
In any case, maybe it is worth revisiting some of the relevant policies
on Fedora packaging. This is not a Firefox-specific issue; GNOME,
Emacs, etc. also have packaged addons.
As far as browser updates "breaking" addons... you're inferring a "tail wagging the dog"
scenario. That just isn't appropriate. Addons aren't core browser functionality. If they
were, they wouldn't be addons. Same logic would apply to GNOME, etc. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
