1 |
On 29/10/2012 11:10, Rich Freeman wrote: |
2 |
> While I do agree in principle, I think that talking about going to |
3 |
> devrel over "minor inconsistencies" is over-the-top. |
4 |
|
5 |
It's not about the inconsistencies, it's about the excuse. If the |
6 |
maintainer owns up to the mistake, that's fine by me, shit happens and |
7 |
so on. If the maintainer tries to cover behind "I'm just proxying", then |
8 |
I'll be pissed. |
9 |
|
10 |
> I'll take a package that has a mistake twice a year over a package |
11 |
> that isn't in the tree at all any day. |
12 |
|
13 |
That's fine if it's a fringe package or one that wouldn't get to the |
14 |
tree otherwise — I agree with the spirit and methods. It's _not_ fine |
15 |
for a package that, yes, only has 50 dependencies, but every time it |
16 |
breaks everything goes KO. |
17 |
|
18 |
> It seems like many of the ICU issues are upstream-related. If your |
19 |
> library breaks on every release then somebody clearly doesn't |
20 |
> understand the purpose of sonames. That puts anybody maintaining the |
21 |
> package at a distro level in a really bad position. |
22 |
|
23 |
The problem with ICU is worse than you expect. For once, with version |
24 |
50, it changes ABI (but not soname as far as I can tell) depending on |
25 |
which compiler you build it with. Yes, this is pretty much fucked up. |
26 |
|
27 |
> I think what is most needed here is a maintainer that can just |
28 |
> coordinate with the various downstream projects. I don't care as much |
29 |
> whether ICU is perfectly consistent as long as projects like chromium |
30 |
> have a chance to test things out and catch issues before they hit the |
31 |
> tree. That is actually part of the job of a proxy maintainer. |
32 |
|
33 |
Agreed. At the same time, we should have learnt that Arfrever is unable |
34 |
to take up that job, given the repeated issues we've been having with |
35 |
almost everything he maintained. Which is why we need to find someone else. |
36 |
|
37 |
-- |
38 |
Diego Elio Pettenò — Flameeyes |
39 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |