Re: git: 4df0e66a3662 - main - llvm.mk: add export/noexport to handle CC/CXX/CPP exports

> On Sep 13, 2023, at 8:22 AM, Alexey Dokuchaev <danfe@freebsd.org> wrote:
> 
> On Wed, Sep 13, 2023 at 08:04:27AM +0200, Tobias C. Berner wrote:
>> On Wed, 13 Sept 2023 at 07:56, Gleb Popov wrote:
>>> On Wed, Sep 13, 2023 at 8:20???AM Tobias C. Berner wrote:
>>>> USES=llvm.mk now supports 'export' (default) and 'noexport' arguments.
>>>> When export is set, CC, CXX and CPP will be set to the path corresponding
>>>> to the chosen llvm-version.
>>> 
>>> The choice for the default seems strange to me. Now every port that
>>> has USES=llvm will be switching to building with a non-base compiler.
>>> Is this really a sensible default?
>> 
>> From a rough count: of the 87 ports using llvm.mk 50 set CC.
> 
> That's probably because of all those knee-jerk silly attempts to unbreak
> the ports' build against new Clang.  I've hunt down and whacked some of
> them, but quite a few are still there, waiting to be replaced with a proper
> fix.  So at the end of the day I agree with Gleb, it's a dubious default.
> 
> ./danfe

The problem with you is you cannot see the world at a wider angle.

While you are all about whining/badmouthing in your commit log with those fixes, you did not count that we have an official RELEASE 14 to make which should come with as less broken port as possible. We are fighting with a timeline not your proper fixes which can be done any moment at a later time without using improper word in a commit log.

It's a whole new world out there; try to adopt to it.

Kind regards,
Moin(bofh@ with all hats off)