How are pkgbase & port-packages updates supposed to be handled for the likes of libmd.so.6 -> libmd.so.7 ?

The main [so: 15] contexts are for both of the following sorts of
sequences. . .


More frequent system updates, so:

) libmd.so.7 1st being created before __FreeBSD_version was incremented
   (30 Sep 2024 03:36:04 UTC .. 30 Sep 2024 19:59:43 UT commits)

Update here

) __FreeBSD_version was incremented because of libmd.so.7 being created
   (02 Oct 2024 19:56:06 UTC)

Update here


Vs.: Less frequent system updates, so:

) libmd.so.7 1st being created before __FreeBSD_version was incremented
   (30 Sep 2024 03:36:04 UTC .. 30 Sep 2024 19:59:43 UT commits)

No update here

) __FreeBSD_version was incremented because of libmd.so.7 being created
   (02 Oct 2024 19:56:06 UTC)

Update here


I have omitted references to when port packages are distributed that
depend on libmd.so.7 : those build contexts have their own timing
on the build servers. But consider aarch64 (Tier 1) that could take
something like 2 weeks before there is a distribution based on a system
that has libmd.so.7 (and possibly longer before a build that would
also have had the __FreeBSD_version increment involved).


Is the intended technique of handling such well documented for
PkgBase contexts?


Note:

I'm not asking about dealing with landing in the middle of the commit
sub-sequence related to:

-SHLIB_MAJOR= 6
+SHLIB_MAJOR= 7

that was just over 30 Sep 2024 03:36:04 UTC .. 30 Sep 2024 19:59:43 UT .

===
Mark Millard
marklmi at yahoo.com