Re: Re: FreeBSD ports community is broken

* 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.

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.

-- 
 Felix Palmen <zirias@FreeBSD.org>     {private}   felix@palmen-it.de
 -- ports committer --                     {web}  http://palmen-it.de
 {pgp public key}  http://palmen-it.de/pub.txt
 {pgp fingerprint} 6936 13D5 5BBF 4837 B212  3ACC 54AD E006 9879 F231