Re: awk behaviour?

Am 29.07.21 um 18:42 schrieb Michael Butler via freebsd-current:
> On 7/29/21 6:09 AM, Michael Gmelin wrote:
>>
>>
>> On Wed, 28 Jul 2021 16:02:30 -0400
>> Ed Maste <emaste@freebsd.org> wrote:
>>
>>> On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
>>> <freebsd-current@freebsd.org> wrote:
>>>>
>>>> What prompted the question was my (obviously poor) attempt to debug
>>>> and resolve this failure when attempting to build a release for
>>>> i386 on an amd64 ..
>>>
>>> This will be due to my 4e224e4be7c3. I'm not sure exactly what's
>>> happening yet, but I can provoke this behaviour if `${PKG_CMD}
>>> --version` outputs something other than a single line with the version
>>> number.
>>>
>>
>> Could it be, that the pkg binary isn't installed in $LOCALBASE/sbin/pkg,
>> (whatever LOCALBASE is at that point)? This would make pkg --version
>> shows its bootstrap message:
>>
>>    The package management tool is not yet installed on your system.
>>    Do you want to fetch and install it now? [y/N]:
>>
>> which could explain the behavior.
>>
>> Just speculating...
> 
> This is consistent with the behaviour I'm now seeing after the most recent patch.
> 
> In the chroot environment used by a cross-compilation, there is no installed
> pkg port. When pkg is invoked in the target environment, it now waits on the
> yes/no response,

Passing "ASSUME_ALWAYS_YES=yes" in the environment should cause the
installation to proceed without a wait for user input.

Regards, STefan