Considering devel/glib20: Shouldn't ports(7) also contain a mention of FLAVOR= ?

[ShelLuser]

Hi gang!

So in case you're wondering what this is all about... I'm referring to issue 20250402 in /usr/ports/UPDATING:

  New versions of glib started to require gobject-introspection as a build
  dependency, while gobject-introspection requires glib to build. This forms a
  dependency cycle that is dealt with by introducing the @bootstrap flavor for
  mentioned ports. This solution is suggested by the upstream as well, see
  https://discourse.gnome.org/t/dealing-with-glib-and-gobject-introspection-circular-dependency/18701

See, at the end of the update instruction it mentions the option to issue #pkg remove glib-bootstrap gobject-introspection-bootstrap to clean everything up afterwards, which works.

However... although devel/gobject-introspection builds cleanly after this devel/glib20 does not (note: on the latest Ports branch, so this could be simply caused by a hiccup).

Now, it's not the building which I want to address, but rather the involved documentation.

See, flavors have existed within the Ports collection for some time now (see Chapter 7 of the Porters handbook) however there's no mention at all about this within ports(7) other than the 3rd example:

     Example 3: Building a Non-Default Flavor of a Port

       The following command builds a non-default flavor of a port.  (In this
       case devel/py-pip is going to be built with Python 3.7 support.)

         # cd /usr/ports/devel/py-pip
         # env FLAVOR=py37 make build

... but wouldn't this make much more sense if FLAVOR= would actually have been mentioned within the list of Environment options?

I'm studying the commitors guide as we speak, but figured it might also make an interesting subject for discussion.