At 2022-04-04T03:43:37+1000, G. Branden Robinson wrote: > Long story short, we need font/device description directory stamp > files for each output device that generates any such files at build > time and for which we render groff documents in the build tree, and > documents so rendered need to declare dependencies on these stamp > files. Some of this is already done, but the naming practice is > haphazard and I am not convinced that the dependencies are declared > everywhere they should be. The Savannah ticket is suggestive evidence > that they're not.
For those not following the groff-commit list (which I encourage readers of this list to do), the foregoing is done. Nearly all of the 27 commits I pushed on 3 May[1] improve the build dependency situation. There are fewer spurious rebuilds, more accurate dependency declarations, and more potential parallelism. Does anyone know of any further build system work that should be done before 1.23.0.rc2? I can't think of any. My preference would be not to fool with the build system any more between RC2 and final, except maybe to address the following issues specifically. We still need feedback from John Gardner on Savannah #62357. (Or someone with a macOS environment that doesn't support UTF-8(?).) I don't regard Savannah #60217, #60613, #61709, or #62275 as gating for this RC. If someone disagrees, please speak up. Here's a Savannah bug-lookup URL template. <https://savannah.gnu.org/bugs/?99999> Regards, Branden [1] https://lists.gnu.org/archive/html/groff-commit/2022-05/index.html
signature.asc
Description: PGP signature
