Fossil

• FOO can now point to both a flat directory as before or to a directory one level up with lib/ and include/ subdirs, as zlib installs to when configured with a --prefix, fixing an issue reported on the forum.
• The old method would check the default paths before trying what you gave it, preventing local overrides when you know the platform version isn't what you want and you've built from source, then pointed Fossil at the replacement. It isn't always safe or advisable to remove the platform version in this case merely to get Fossil's configuration script to move on and obey your explicit directive.
• The old method checked for the header and the library in a single step, resulting in unhelpful configure output, requiring that one dig through config.log to figure out what happened.

As discussed with Stephan in /chat. File objects in the renamed case possess a 'priorName' property in addition to the 'name' reported in all cases. (check-in: f8d6e8c12a ... user: mark tags: trunk)

As reported by larrybr on the forum: 9e9778f2e6, 'fossil json status' reports renamed _and_ edited files as only renamed. This change reports such cases as both edited and renamed, and displays the filename prior to being renamed as well as the renamed path. We now also update the vfile table before generating the status report to ensure the current checkout state is reported. (check-in: 771e592b4c ... user: mark tags: trunk)

In `fossil {changes,status}` and the commit description shown in the editor with `fossil commit`, show the original and renamed path annotation if the file has been renamed and edited. Prior to this, the file was only reported as edited, which can be confusing. Reported by James Cook 5a4c530e6b. Discussed with stephan@ and danield@, plus some forum members. While here, make sure we honour the relative-paths setting/option when displaying the original pathname in the renamed case. (check-in: ca9d0ddf06 ... user: mark tags: trunk)

This fixes an issue reported by James Cook in d162b6e2dc. Previously, we assumed the fx_git table does not exist when creating a new import, thus the previously untested use case of importing multiple new (read: not incremental) git repos into the same fossil repo failed at this assumption. While here, document the persistent nature of attributions in the import cmd help text; previously, this was only in the online docs: /doc/trunk/www/inout.wiki (check-in: 47fb3ddc5a ... user: mark tags: trunk)

Tested on OpenBSD 7.3-current and macOS Ventura 13.4 by me, and also on some Linux machines by stephan@

This automatically generates a compile_commands.json file on machines that support the -MJ clang compiler option, which can be consumed by language server clients. (check-in: 91f0f00f5d ... user: mark tags: trunk)

Reported by James Cook in 2b857ded1b: renamed files were shown as a deletion and an addition. This was because the optional 3rd and 4th field in the manifest's F card to indicate renames were omitted, despite having parsed these data from the git fast-export marks. (check-in: 7ab1e11850 ... user: mark tags: trunk)

As per James Cook's report in 2b857ded1b, the /info page provided no hint that a renamed and modified file had been renamed, only modified. This slightly changes the annotation to make it clear the file was also renamed. Discussed with larrybr and stephan in /chat. Slight tweak on stephan's suggested phrasing.

ok stephan@ (check-in: 495a4d71b8 ... user: mark tags: trunk)