Resolved issues #1233 and #1218

CHANGES.md

@@ -1,6 +1,39 @@
 # Major changes to the IOCCC entry toolkit
 
 
+## Release 2.4.5 2025-03-10
+
+Add `-U UUID` option - resolve #1229.
+
+Also fixed an error with `-u uuidfile` where it would not set the `test` boolean
+to true if the UUID was `"true"`.
+
+The `-u uuidfile` and `-U UUID` options may not be used with `-i answers`, `-d`
+or `-s seed`.
+
+Partial fix to issue #1208. The `-x` option to force delete the
+submission directory and `-r rm` option to set path to `rm(1)` were added to
+`mkiocccentry` as part of #1208. The change in order of args is **NOT** done and
+will not be done until **AFTER** IOCCC28.
+
+Fixed bug where `overwrite_answers` was always true by default (`mkiocccentry`).
+
+Updated man page for the above changes.
+
+Resolved issues #1233 and #1218. Both `mkiocccentry` and `txzchk` (the only ones
+that use other tools) now search `$PATH` for the tools first by way of the
+`find_utils()` function (modified a fair bit) and a new util function in jparse
+called `resolve_path()`. The jparse util functions `shell_cmd()` and
+`pipe_open()` were also improved to resolve paths if no `/` is in the command
+name. As for `make`: we now search for `gmake` first as the Makefiles we need
+are GNU Makefiles.
+
+Add missing `-r` to `rm` in `mkiocccentry_test.sh`.
+
+**IMPORTANT NOTE**: you do NOT need to use this update in order to participate
+in the IOCCC28!
+
+
 ## Release 2.4.4 2025-03-09
 
 Resolve some (mostly top priority) issues.

jparse/CHANGES.md

@@ -1,5 +1,35 @@
 # Significant changes in the JSON parser repo
 
+
+## Release 2.2.35 2025-03-10
+
+Improved `shell_cmd()` and `pipe_open()` to resolve path (using `resolve_path()`
+which searches `$PATH`) if there is no `/` in the command.
+
+Updated `JPARSE_UTILS_VERSION` to `"2.0.5 2025-03-10"`.
+
+
+## Release 2.2.34 2025-03-09
+
+Updated `base_name()`, `dir_name()` and added new function `resolve_path()`.
+
+The function `base_name()` now will, on a NULL or empty string, return a copy of
+`"."` just like `basename(3)` does.
+
+The function `dir_name()` now will, on a NULL or empty string or a string that
+has no `/` (unless `level < 0`) , return a copy of `"."` just like `dirname(3)`
+(though that function does not have the `level` functionality).
+
+The function `resolve_path()` will go through the process's `$PATH` and search
+for an executable file with the name passed to the function, returning either a
+copy of the path or NULL. If the command starts with `/` or `./` then the
+`$PATH` is not searched and instead that exact string is duplicated and
+returned.
+
+Updated `JPARSE_UTILS_VERSION` to `"2.0.4 2025-03-09"`.
+Updated `UTIL_TEST_VERSION` to `"2.0.2 2025-03-09"`.
+
+
 ## Release 2.2.33 2025-03-07
 
 Additional sanity checks added to FTS code.