1 |
Hi All, |
2 |
|
3 |
Far be it from me to flame anyone. I have not been keeping myself as up |
4 |
to date on this list as I should. However, I feel I must comment about |
5 |
the libPNG issue. First off, Spider and I decided to do it. Neither of |
6 |
us is a KDE person, so perhaps we underestimated the amount of hassle it |
7 |
was to be for the KDE folks. |
8 |
|
9 |
As for trolling, I do not think that Mrs. Loli-Queru was trolling. |
10 |
Rather, I think she brought up a valid point, and an obvious weakness in |
11 |
the method that we chose to unleash the libpng update to people. Her |
12 |
point about recompiling X may not have been a literal one, but the |
13 |
_effect_ of the update was as large as that (for KDE users). |
14 |
|
15 |
There has been much discussion about it, and I am confident that such |
16 |
things will not be repeated. We are implementing a methodology that |
17 |
allows smoother transitions. |
18 |
|
19 |
As for the fact that it was a _choice_ to update. Yes, it was. However, |
20 |
users tend to place a certain amount of trust in the distribution. And as |
21 |
such, putting them through a hassle like that is certainly not going to be |
22 |
appreciated. What we did not do as well as we could have was inform the |
23 |
user of the magnanimity (if that is, indeed, a word) of the update. |
24 |
|
25 |
To the users of KDE that were blindsided by this, please accept my |
26 |
apology. And, Mrs. Loli-Quero, despite the obvious weaknesses of |
27 |
open-source, I think that we are striving to make headway and advances in |
28 |
quality control (said libpng experience notwithstanding :), and we can |
29 |
only improve. |
30 |
|
31 |
Thanks, |
32 |
|
33 |
Seemant |