[bug #63900] configuration report regarding wrapped macro packages seems inaccurate

[G. Branden Robinson]

Update of bug #63900 (project groff):

                  Status:                    None => Ready for Merge        
             Assigned to:                    None => gbranden               

    _______________________________________________________

Follow-up Comment #1:


commit 55fe32728db7dbde29d70acd40e2759f5f4a3865
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Fri Mar 17 15:26:38 2023 -0500

    ChangeLog: Add bug closer for Savannah #63900.

commit 5be747f94f81557bb0c802e5b6f723765c497314
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Mon Mar 13 22:31:57 2023 -0500

    m4/groff.m4: Drop garbage space from variable.
    
    * m4/groff.m4 (GROFF_TMAC): Eliminate garbage leading space from
      contents of `tmac_wrap` shell variable.

commit b0188e80c791a339132e8d3cbae884140693b087
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Mon Mar 13 22:23:02 2023 -0500

    [build]: Clarify GROFF_TMAC Autoconf test output.
    
    * configure.ac: Correct characterization of the list of macro packages
      reported.  It is not the list of macro packages receiving a "g"
      prefix, but the list of macro packages reciving a wrapper macro file
      in groff's macro directory, each of which source the corresponding
      system (likely AT&T-descended troff) macro package.  Fixes wording I
      introduced in commit 4d30dd7424, 31 May.
    
    * m4/groff.m4 (GROFF_TMAC): Clarify first "checking" message that we are
      looking for a file name prefix on existing system macro packages (like
      "tmac.").  This has nothing to do with the prefix applied to groff
      commands, or the "g" prefixed to groff implementations of the man, mm,
      and ms packages.  Tighten wording of second "checking" message.
      Consistently say "(none)" instead of "none" or "none found".




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63900>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/