Re: INDEX-12 gotten by portsnap is not updated

From: Colin Percival <>
Date: Fri, 05 May 2023 15:12:37 UTC
On 5/5/23 07:53, Felix Palmen wrote:
> * Colin Percival <> [20230505 07:46]:
>> On 5/4/23 23:47, Colin Percival wrote:
>>> Indeed.  I think I've fixed it by copying a newer /usr/bin/make into the
>>> build environment -- I should be able to confirm whether it works soon.
>> Confirmed, portsnap's INDEX is working again. :-)
> Thanks for letting me know!
> I think I'll still rework that particular commit, just for the sake of
> readability. It *seems* the issue was older make not correctly handling
> AT&T style expansions, but then, they're not that readable either ;)

Older bmake handles ${FOO:%=bar%} with an empty FOO by matching % to the
empty string.  In 2020, NetBSD changed this to non-matching "for gmake

I don't think either approach is wrong per se, but obviously problems can
arise when the behaviour changes. ;-)

Colin Percival
FreeBSD Deputy Release Engineer & EC2 platform maintainer
Founder, Tarsnap | | Online backups for the truly paranoid