Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Feb 2024 17:49:21 +0900
From:      Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
To:        ports@freebsd.org
Subject:   Re: FreeBSD ports community is broken
Message-ID:  <20240218174921.a8082649142dd43a469bebfa@dec.sakura.ne.jp>
In-Reply-To: <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges>
References:  <20240218015843.34c5d078@rimwks.local> <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges>

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

> * Rozhuk Ivan <rozhuk.im@gmail.com> [20240218 01:58]:
> > 1. devel/pkgconf: unconditionally prioritises base system libraries
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273961
> > Actors: <Charlie Li> vishwin@freebsd.org and <Felix Palmen> zirias@freebsd.org
> 
> Actually, the discussion in this PR (which was ridiculously long because
> of one single person) tells the whole story.
> 
> I guess for anyone completely unwilling to even *try* to understand why
> their patches NOT fixing the actual root cause are ugly and potentially
> harmful hacks, trying to "contribute" to ports while stubbornly spamming
> lots of people with needless arguments and in the end even insulting
> people is not a great strategy. I mean, there's always the possibility
> to fork a project if you want.
> 
> -- 
>  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

I "feel" these are came from the differences on backgrounds of each
side.

Just a FYI.

In automotive industry area, once SINGLE defective part is discovered at
customer (GM, Chrysler, Forrd, Toyota, VW,...) side, the supplier must
immediately proceed "corrective action". Even some ppm of devective
parts shipped to customer is considered as "a huge amount of defects".
In many case, corrective action is "additional inspection to stop
shipping defective parts".

And this is not everything to do.
Supplier need to investigate the root cause and decide "preventive
action" while "corrective action" is active.

For persons working on automotive industry, do nothing until preventive
action is made is nonsense. We are forced to do corrective action, even
if it's very, very, ... ,very ugly "addidional inspection".

Moreover, aerospace area is much more stricter than automotive area.

Keeping these in mind, the hack you hate is the "corrective action",
while fixing root cause you like is the "preventive action".
Corrective action is needed for users until preventive action is done.

Note that ugly corrective action can be reverted back once preventive
action is confirmed OK and done.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>



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