Log message:
*: recursive bump for perl 5.34

Log message:
revbump for textproc/icu

Log message:
gtkmm3: updated to 3.24.4

3.24.4 (stable):

The tarball for 3.24.4 has been created with 'meson dist'.
If you build with Autotools from the tarball, please read the relevant
part of the README file.

Build on Windows:
* Gtk::TreePath: Export comparison operators

3.24.3 (stable):

The tarball for 3.24.3 has been created with 'meson dist'.
If you build with Autotools from the tarball, please read the relevant
part of the README file.

Gtk:
* Actionable::get_action_target_value(): Fix ref count

Documentation:
* Improve the documentation of Gtk::Application::add_window()
  and Gtk::Window::set_application()
* Gtk::Button::set_image(): Fix the documentation
* Gtk::TreeView::append_column(): Add code example
* README: Add instructions for building gtkmm
* Explain key values

Demos:
* Don't use C++14 auto deduction
* Update the GLArea demo (similar to updates in gtk+)
* GLArea demo: Fix a crash

Tests:
* Builder test: Test derived props declared in C++

Build:
* Improve NMake support
* Fix Autotools build with X11 backend disabled (--enable-x11-backend=no)
* Use __declspec(dllexport) when building with Visual Studio
* Add support for building gtkmm with Meson
* docs/reference/: Update for Doxygen >= 1.8.16

Log message:
*: Recursive revbump from textproc/icu-68.1

Log message:
*: bump PKGREVISION for perl-5.32.

Log message:
*: revbump after fontconfig bl3 changes (libuuid removal)

Log message:
x11/gtkmm3: restore ABI_DEPENDS as API_DEPENDS

wiz says: Packages are not supposed to set BUILDLINK_ABI_DEPENDS for
other packages, they should set BUILDLINK_API_DEPENDS (P instead of B).

After that change, all these entries actually have an effect since they
are greater than their corresponding default BUILDLINK_API_DEPENDS, and
pkglint no longer complains.

Log message:
x11/gtkmm3: move gtk3 buildlink above the PKG_BUILD_OPTIONS

Before, "bmake show-all" showed that PLIST.x11 was commented out.  This
was misleading since during the actual package build, that variable is
active, and the corresponding files are included in the PLIST.

This inconsistency was due to the magic of MAKEVARS and the barrier.

When bmake is run, the build options of gtk3 are determined and added
to MAKEVARS.  At that point PLIST.x11 is still undefined.  That doesn't
matter since this variable is not evaluated yet.  Before the actual PLIST
generation happens, the value of PKG_BUILD_OPTIONS.gtk3 is stored in
work/.build_makevars.mk, which acts as a cache.

After that, the barrier steps in, and bmake calls an inner bmake to do
the actual work.  This inner bmake reads the package Makefile again, and
when bsd.prefs.mk is included, the makevars.mk cache is loaded as well.
This makes PKG_BUILD_OPTIONS.gtk3 known at load time, and at that point,
PLIST.x11 is evaluated as expected and becomes "yes".

Luckily, PLIST.x11 was not added to MAKEVARS.  Otherwise it would have
been evaluated too early, the early value would have been cached, and the
whole trick wouldn't have worked.

Log message:
x11/gtkmm3: remove redundant dependencies

pkglint says:

NOTE: Makefile:30: The requirement >=2.24.2 is already guaranteed by the \ 
>=2.24.3nb2 from ../../devel/atkmm/buildlink3.mk:11.
NOTE: Makefile:33: The requirement >=2.49.1 is already guaranteed by the \ 
>=2.62.0nb1 from ../../devel/glibmm/buildlink3.mk:9.
NOTE: Makefile:36: The requirement >=2.38.2 is already guaranteed by the \ 
>=2.42.0nb3 from ../../devel/pangomm/buildlink3.mk:9.
NOTE: Makefile:38: The requirement >=1.12.0 is already guaranteed by the \ 
>=1.12.2nb3 from ../../graphics/cairomm/buildlink3.mk:9.
NOTE: Makefile:40: The requirement >=2.35.5 is already guaranteed by the \ 
>=2.40.0nb1 from ../../graphics/gdk-pixbuf2/buildlink3.mk:9.
NOTE: Makefile:43: The requirement >=3.22.0 is already guaranteed by the \ 
>=3.24.14nb2 from ../../x11/gtk3/buildlink3.mk:9.

Log message:
Revbump for icu