Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump?

[Tatsuki Makino]

David Wolfskill wrote on 2020/10/06 08:45:

> 
> But in order for them to be built, you need to have updated
> ports-mgmt/pkg ahead of time, or this kind of thing happens:
> 
> | ...

> | ===>  Cleaning for nvidia-driver-440.100_1
> | ===>  nvidia-driver-440.100_1 pkg(8) must be version 1.15.9 or greater, but
> | you have 1.15.8. You must upgrade the ports-mgmt/pkg port first.
> | *** Error code 1
> | 
> | Stop.
> 

Hmmm.
I've never bothered with that because I'm following the steps below :)

svnlite cleanup /usr/src
svnlite update /usr/src
rm -r -f /usr/obj/{*,.[^.]*,..?*}
svnlite revert -R /usr/src
patch -d /usr/src < mypatch
portsnap fetch update
portmaster -x \*-kmod-\[0-9gv\] -a
make -C /usr/src buildworld
make -C /usr/src buildkernel
mergemaster -p
make -C /usr/src installkernel
make -C /usr/src installworld
make -C /usr/src delete-old delete-old-libs
mergemaster
shutdown -r +1

> 
> Hence my query: Is an UPDATING entry warranted when MINIMAL_PKG_VERSION is
> bumped?
>

Normally, when pkg appears in pkg version -L =, it is replaced
immediately because something of a bug in it has been fixed.
Rarely, though, there are more bugs :)

Best regards.