| 1 |
On Wed, 31 Oct 2012 11:58:16 -0700 |
| 2 |
Diego Elio Pettenò <flameeyes@×××××××××.eu> wrote: |
| 3 |
|
| 4 |
> On 31/10/2012 11:49, Michał Górny wrote: |
| 5 |
> > In other words, you have thrown a big, destructive change to live, |
| 6 |
> > stable systems without prior testing (and don't say you were able to |
| 7 |
> > test it thoroughly in one day's time) and you have left them for other |
| 8 |
> > people to maintain and fix. |
| 9 |
> > |
| 10 |
> > I am really getting tired of those 'senior developers' who believe that |
| 11 |
> > Gentoo is their private playground where they can do whatever comes |
| 12 |
> > into their mind and ignore package maintainers. |
| 13 |
> |
| 14 |
> Given the kind of destructive behaviour that boost has been having, |
| 15 |
> given that everybody else _beside you_ don't see any reason to keep that |
| 16 |
> slotted boost, given that you've been acting for the most part as a |
| 17 |
> sockpuppet for a developer who's been kicked out of Gentoo, I think it's |
| 18 |
> obvious why I went the way I went. |
| 19 |
|
| 20 |
If you have a personal vendetta against Arfrever, then take it to him. |
| 21 |
As far as I'm concerned, Arfrever is a very knowledgeable person and I |
| 22 |
doubt that you can compete with him in the area of Python |
| 23 |
(and the Python counterpart of boost, effectively). |
| 24 |
|
| 25 |
And even if that, you have no right to remove maintainers |
| 26 |
from a package or unCC them from bugs just because you don't like them |
| 27 |
or disagree with their opinion. Especially that you are not |
| 28 |
a maintainer of this package. |
| 29 |
|
| 30 |
> Here's the deal: I've stated clearly what the situation was going to be; |
| 31 |
> Tiziano has been the primary maintainer (first in the list) and he's |
| 32 |
> okay with the move, he _is_ in the cpp herd that will take care of it, |
| 33 |
> and as I said I'll make sure to help out because I have a number of |
| 34 |
> packages depending on boost (but not on other C++ libraries). |
| 35 |
|
| 36 |
Sorry, I didn't notice his reply. That's my mistake. |
| 37 |
|
| 38 |
> You had a month while Mike delayed glibc-2.16 stable, among other things |
| 39 |
> because of boost-1.50, and you did _squat_ to handle it. So it's time |
| 40 |
> that people who've been there before step up and fix it the way that it |
| 41 |
> has to be fixed. |
| 42 |
|
| 43 |
Is this something like 'people didn't fix issues yet, so let's throw |
| 44 |
the issues at users to motivate them'? |
| 45 |
|
| 46 |
-- |
| 47 |
Best regards, |
| 48 |
Michał Górny |
Archives