doc: Reference POSIX:2024 for rm -f future requirement.

* NEWS-future: The previously "next" POSIX version is the current
POSIX (2024) now, requiring rm -f to be a no-op.

diff --git a/NEWS-future b/NEWS-future
index 6f6dbdc15f3d9baf6fc1ea534785692479fe24b2..ae69f952366cc1e8e34702a846a51f65281ce7cf 100644 (file)
--- a/NEWS-future
+++ b/NEWS-future
@@ -11,17 +11,16 @@ Therefore, there is no ETA for Automake 2.0, and it is not likely to be
 any time soon.  So moving these future issues to a separate file seemed
 warranted.  For more info, see the ./PLANS/ directory.
 
-
 * WARNING: Future backward-incompatibility!
 
   - Makefile recipes generated by Automake 2.0 will expect to use an
     'rm' program that doesn't complain when called without any non-option
     argument if the '-f' option is given (so that commands like "rm -f"
     and "rm -rf" will act as a no-op, instead of raising usage errors).
-    This behavior of 'rm' is very widespread in the wild, and it will be
-    required in the next POSIX version:
-
-      <http://austingroupbugs.net/view.php?id=542>
+    This behavior of 'rm' is widespread in the wild, and is required by
+    POSIX as of 2024:
+      <https://pubs.opengroup.org/onlinepubs/9799919799/utilities/rm.html>
+      <https://austingroupbugs.net/view.php?id=542>
 
     Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
     that the default 'rm' program in PATH satisfies this requirement,