increasing cmake requirement?

[Greg Troxel <gdt%lexort.com@localhost>]

Thierry Laronde reported on pkgsrc-users that ancient cmake (3.9!!) was
used in a build of 2023Q2.  Clearly building a package while other
packages are 5 years out of date is not all that likely to work and I
don't think we should worry about it.

Every upstream has its own cmake requirement.  I don't think we have a
need to cross into expressing those; too much cost for too little
benefit.

So, the question is what version is a blend of good enough for most
pacakges while not causing very many to have to upgrade a "perfectly
good cmake".  I picked "end of 2020" as a time when I feel ok to say to
someone having trouble "don't do that then" while also feeling ok about
saying "if a package doesn't build with that the upstream is buggy".
That lands at 3.19.

So, I am inclined to commit this, not do any kind of other changes (no
revbumping), and not worry further.

Does this seem ok, too agressive in time, broken in some way I don't
understand, or ?

I will assume it is ok 3 days from sending this mail absent
comments/objections.  (It's easy to revert if not.)


--- replace.mk.~1.299.~	2023-06-29 06:14:45.281656313 -0400
+++ replace.mk	2023-07-21 06:44:44.684825717 -0400
@@ -322,7 +322,7 @@ _TOOLS.cmake=	cmake cpack
 .    if ${PKGPATH} == devel/cmake
 MAKEFLAGS+=			TOOLS_IGNORE.${_t_}=
 .    elif !empty(_TOOLS_USE_PKGSRC.${_t_}:M[yY][eE][sS])
-TOOLS_DEPENDS.${_t_}?=		cmake>=2.8.1nb1:../../devel/cmake
+TOOLS_DEPENDS.${_t_}?=		cmake>=3.19:../../devel/cmake
 TOOLS_CREATE+=			${_t_}
 TOOLS_PATH.${_t_}=		${TOOLBASE}/bin/${_t_}
 .    endif

-- 
    Greg Troxel <gdt%lexort.com@localhost>