Time to say goodbye to Tiger?

[Gagan Sidhu]

does anyone notice that, ken seems to think he can attack others because he undertakes a larger role than anyone wants?

as we see below, he gets upset when someone shares their own opinion and threatens to stop contributing.

and who’s to say that the month-plus he spent on gcc-14 wasn’t a nightmare of his own creation, since he loves playing hero ball?

he has previously conceded there are header clashes with his macports-libcxx contribution that prevent people from using the legacy portgroup flag the way it was intended, where the workaround is manually linking the library “by hand”.

i wouldn’t be surprised if a lot of the problems or shakiness are culminations of his decade-plus mediocrity.

what’s sad is he cannot appeal to authority on his own merits, previously deferring to jeremyhu’s merits since he was an APPUL developer. using others as a shield for his own shortcomings.

you can’t even play hero ball properly, man. look in the mirror. where is your merit and authority to which the rest of us can rely?

you make this project suck. i’ve heard it from others too.

to be honest, i wonder how many contributors this project has lost over the past decade because of his uncivilised behaviour.

i have a useful PR that sits open because your poor attitude. now people on older macs can’t even use a newer gdb (not like it’s a HUGE difference, but still, every bit counts).

deflect, deny, demean. those are Ken’s “Three Ds”

god he’s so tiring. 

> On Jan 26, 2025, at 5:11 PM, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
> 
>> Except of course when someone decides to inflict a 
>> new compiler on it when the old one was working fine.
>> 
>> Fred Wright
> 
> Yes, after I last updated the gcc ports on older systems, I also then left gcc-7 as the default compiler for a very very long time specifically to avoid problems -- and very successfully, I would say.
> 
> However, barracuda and others were very (very very very very) enthusiastic about pushing the compiler up to gcc-14, and I started to fear that it was going to get pushed in a hopelessly broken state that would completely break everything, unless someone stepped up to make sure it was done correctly.
> 
> There was indeed considerable risk of this at points.
> 
> So I did spend nearly a month of my own time shepherding the upgrade to gcc-14 so that it would be done right, and not in a shabby, broken fashion.
> 
> And it was, in the end, done right I think, with as little uproar as there could have been with such a jump.
> 
> Of course, had I known we were about to drop Tiger I would not have spent so much time making sure Tiger survived the upgrade, certainly.
> 
> As previously mentioned, I am sorry you missed the 287 posts in the PR to upgrade the compiler, and the dozens of mailing list messages about the upgrade.
> 
> I suppose I could have reached out specifically emailed you asking for your opinion.
> 
> To avoid this from happening in the future, you could become the maintainer of the gcc ports if you like. I think we would all appreciate that, and then you could be in charge of everything forever and this would never, ever happen to you again.
> 
> Ken