Minor fixes to FAQ wrt other repos

The FAQ now notes that there can be times where the jparse repo
(https://github.com/xexyl/jparse/) is different from the mkiocccentry
repo's subdirectory jparse. This is one of the reasons the tools in the
mkiocccentry and the jparse repo show the jparse API with the -V
(version) option.

I believe that this is all that's needed for the jparse repo in the FAQ
but time will tell on that.
This commit is contained in:
Cody Boone Ferguson committed 2024-09-07 09:39:51 -07:00
1 parent 69bef8add2
commit 79e3f18ed6
2 files changed
+14 -6

No files matched your search

+7 -3
View File
@@ -1426,9 +1426,13 @@ If you want to validate the `.auth.json` or `.info.json` files you
should use `chkentry(1)` from the [mkiocccentry
repo](https://github.com/ioccc-src/mkiocccentry).
The `chkentry(1)` tool uses the
[jparse API](https://github.com/ioccc-src/mkiocccentry/blob/master/jparse/man/man3/jparse.3)
API to perform **additional** checks on these two IOCCC specific JSON files.
The `chkentry(1)` tool uses the IOCCC version of the [jparse
API](https://github.com/ioccc-src/mkiocccentry/blob/master/jparse/man/man3/jparse.3)
to perform **additional** checks on these two IOCCC specific JSON files. It is
_possible_ that this version will at times differ from the [official jparse
API](https://github.com/xexyl/jparse/blob/master/man/man3/jparse.3) at the
[official jparse repo](https://github.com/xexyl/jparse) and this is one of the
reasons the tools' `-V` (version option) show the JSON parser version as well.
See the
FAQ on "[.auth.json](#auth_json)"