any reason to keep cmake at v3?

[RJVB (René Bertin)]

I saw that upstream is well into 4.x at the moment. I know there have been changes to how CMake can be used by IDEs but AFAICT features like the cmake server mode have been unavailable in v3 for a while too. From what I can tell the make and ninja generators continue to be available which are the only two available via the CMake-1.1 PG.

Are there any reasons to keep the port at v3.31.10 ? ("Too time-intensive to update" would be an understandable answer ;) but I fear that the work will have to be done at some point...)

[ryandesign (Ryan Carsten Schmidt)]

Some ports fail to build with cmake 4, e.g. #73392. I guess the thought was to try to identify and fix as many of those as we can (using cmake-devel) before updating cmake.

[RJVB (René Bertin)]

yeah, that's probably the most frequent reason why building (or rather, configuring) would fail.

I've offered some suggestions on that ticket, but it would also be possible to add a port:cmake3 (probably installed as cmake3) if it turns out that there are other issues which can't be solved through a cmake PG workaround and/or simple patching of the dependent port. (For the latter approach, the Arch and/or Gentoo packaging must already contain all the required info!)

Meanwhile, I'm not in a hurry to upgrade, my own version of the port is still at 3.29.2 (i.e. it still has a patchfile for a feature I contributed myself ... sadly they weren't interested in my patch that enables the bootstrap script to use the currently installed cmake binary instead of building a bootstrap version...).