1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRPM%5D%20cauldron%0A%09core/release%09firefox-ext-add-on-compatibility-reporter-0.9-1.mga2&In-Reply-To=%3C4E57F1BC.6020908%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007569.html">
<LINK REL="Next" HREF="007560.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRPM%5D%20cauldron%0A%09core/release%09firefox-ext-add-on-compatibility-reporter-0.9-1.mga2&In-Reply-To=%3C4E57F1BC.6020908%40laposte.net%3E"
TITLE="[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2">andr55 at laposte.net
</A><BR>
<I>Fri Aug 26 21:19:24 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="007569.html">[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2
</A></li>
<LI>Next message: <A HREF="007560.html">[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7570">[ date ]</a>
<a href="thread.html#7570">[ thread ]</a>
<a href="subject.html#7570">[ subject ]</a>
<a href="author.html#7570">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Florian Hubold a écrit :
><i> Am 26.08.2011 09:50, schrieb Sander Lepik:
</I>>><i> 26.08.2011 10:27, Guillaume Rousse kirjutas:
</I>>>><i> I don't see where it is stated than firefox can't get updated until
</I>>>><i> all extensions in the distributions work with it.
</I>>><i> I would call it a regression that shouldn't pass QA. One day your ads
</I>>><i> ands scripts are blocked and the other day they are not. Great user
</I>>><i> experience..
</I>>>><i> The large advantage of packaged extensions is that they are managed
</I>>>><i> by sysadmins, instead of users, which makes a difference when they
</I>>>><i> are different people.
</I>>><i> And even larger disadvantage comes in when they are not updated.
</I>>><i> Contain memory leaks and so on. The biggest problem here is that the
</I>>><i> packager who imported those addons is not keeping them up-to-date.
</I>>><i>
</I>>><i> Sysadmin can copy those extensions into place anyway. Then it's up to
</I>>><i> him/her to keep them up-to-date. Currently we have to take care of
</I>>><i> that and we don't (or if anyone wants to claim that we do then we do
</I>>><i> it really poorly as there are already newer versions of addons that
</I>>><i> got pushed with latest update).
</I>>><i>
</I>>><i> --
</I>>><i> Sander
</I>>><i>
</I>>><i>
</I>><i> Well, as there are mostly no bigger changes like in %files, can't an
</I>><i> update of those addons
</I>><i> be scripted or automated halfway? So someone just needs to push this
</I>><i> prior to a Firefox update?
</I>><i>
</I>><i> Not saying i have an opinion pro or against packaged addons, but it is
</I>><i> really a nuisance
</I>><i> as those who do the Firefox update also need to update all those addons,
</I>><i> which is unfair,
</I>><i> seems to me if it's not the importer/maintainer of those addons who does
</I>><i> the update.
</I>><i>
</I>I don't know how mageia-packaged firefox has changed things, but official ff
now automatically accepts any extensions that are compatible, updating their
version compatibility, and disables those using statements no longer
compatible. For individual users, this should be more than adequate, since the
extension manager can be used to update extensions as necessary. (As well as
automatic notification. I would recommend that most ordinary users rely on
ff's buildin extension manager, unless they are maintaining more than 1 computer.
Although I often forget about it, the case where administrators manage software
installation, and not ordinary users, updates are somewhat different -- but sys
admins would be able to deal with it (by downloading the extension and
installing locally) whenever the extension package is not yet available. So
although it may be inconvenient, missing extension packages is not a blocker.
Note that it would be preferable that we package ff so that compatible
extensions are automatically updated, if possible. (Maybe that is already the
case.)
If ff is so packaged, packaging extensions becomes less urgent.
BTW, I would suggest that packaged extensions contain a note that recommends
that ordinary users use ff's buildin extension manager to install extensions.
Note that ff extensions will now normally install in seamonkey (iceape) as well.
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007569.html">[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2
</A></li>
<LI>Next message: <A HREF="007560.html">[Mageia-dev] [RPM] cauldron core/release firefox-ext-add-on-compatibility-reporter-0.9-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7570">[ date ]</a>
<a href="thread.html#7570">[ thread ]</a>
<a href="subject.html#7570">[ subject ]</a>
<a href="author.html#7570">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
