Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Feb 2024 09:45:47 +0200
From:      Rozhuk Ivan <rozhuk.im@gmail.com>
To:        Felix Palmen <zirias@freebsd.org>
Cc:        ports@freebsd.org
Subject:   Re: FreeBSD ports community is broken
Message-ID:  <20240219094547.7cc05361@rimwks.local>
In-Reply-To: <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi>
References:  <20240218015843.34c5d078@rimwks.local> <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges> <20240218174921.a8082649142dd43a469bebfa@dec.sakura.ne.jp> <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Feb 2024 11:16:33 +0100
Felix Palmen <zirias@freebsd.org> wrote:

> * Tomoaki AOKI <junchoon@dec.sakura.ne.jp> [20240218 17:49]:
> > [a lot about automotive regulations]  
> 
> That's a nice example how comparisons of entirely different domains
> almost always go completely wrong.
> 
> To start with, cars (and especially individual parts) typically aren't
> subject to consumer customizations, and if they are, it's way outside
> the manufacturer's responsibility.  Here, we were talking about
> breakage that only happened when you customized your port builds. We
> aren't talking about security-relevant breakage either.

A lot of words instead of a simple recognition of a mistake.


> As explained in the PR as well, of course we add (temporary)
> workarounds to *individual* ports when it seems necessary. We
> certainly don't add workarounds to the framework itself unless it's
> perfectly clear there will be no other way. Not even considering yet
> that just fiddling with CFLAGS has the potential to break a lot of
> other things when done globally.
> 
> All I have left to say is seeing a toxic thread like this is a very
> frustrating experience. So, I'll now move on to something else.
> 

This is an erroneous policy leading to the loss of trust and users.
Ports should work, the rest is not important.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240219094547.7cc05361>