bugGNU troff - Bugs: bug #52443, mdoc macros are too hard to test...

 
 

bug #52443: mdoc macros are too hard to test in-tree

Submitted by:  G. Branden Robinson <gbranden>
Submitted on:  Sun 19 Nov 2017 03:37:59 AM UTC  
 
Category: Macro - mdocSeverity: 3 - Normal
Item Group: Build/InstallationStatus: Duplicate
Privacy: PublicAssigned to: G. Branden Robinson <gbranden>
Open/Closed: ClosedPlanned Release: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Tue 21 Nov 2017 08:26:39 AM UTC, comment #6:

Ah, I see that this is a duplicate of #51003.

G. Branden Robinson <gbranden>
Project MemberIn charge of this item.
Sun 19 Nov 2017 05:38:55 PM UTC, comment #5:

Err sorry, right now, mdoc is still partially stripped. But the cp(1) method i described does work because doc- is no longer stripped.

Ingo Schwarze <schwarze>
Sun 19 Nov 2017 05:35:22 PM UTC, comment #4:

This is not really an important issue in practice. Given that test-groff is subtly different from real groff, and the git directory structure will be different from an installation even after tweaking the git structure or the build system, anybody committing changes will have to test in the installed form anyway.

For quick intermediate tests, now that the macros are no longer stripped, you can simply edit the installed versions during development and copy back to the source tree before commit. Or equivalently edit in the source tree and use pure cp(1) of the one file you edited before each quick test.

If you want to fix the very minor inconvenience anyway, Werner's suggestion seems simplest and clearest.

Ingo Schwarze <schwarze>
Sun 19 Nov 2017 05:58:21 AM UTC, comment #3:

I suggest to simply move the mdoc files into a separate tmac subdirectory – no symlinks at all.

Werner LEMBERG <wl>
Project Administrator
Sun 19 Nov 2017 05:29:57 AM UTC, comment #2:

Yeah, I fully expect that to work, but why create a directory and 4 symlinks when you can create just 1 symlink?

G. Branden Robinson <gbranden>
Project MemberIn charge of this item.
Sun 19 Nov 2017 05:15:47 AM UTC, comment #1:
Bjarni Ingi Gislason <bjarniig>
Sun 19 Nov 2017 03:37:59 AM UTC, original submission:

tmac/doc.tmac-u says the following:

...but these references don't resolve even after the tree is built. They only work after installation somewhere else. Even test-groff(.in), which sets GROFF_TMAC_PATH, is no help because these msos demand a directory called mdoc.

A workaround would be for the build process to make a symlink in tmac called mdoc which points back to ".", and have the clean rule get rid of that symlink.

Any better ideas?

If not, I'll see if I can figure out how to persuade Automake to do what I want.

G. Branden Robinson <gbranden>
Project MemberIn charge of this item.

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by schwarze (Posted a comment)
  • -unavailable- added by wl (Posted a comment)
  • -unavailable- added by bjarniig (Posted a comment)
  • -unavailable- added by gbranden (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 21 Nov 2017 08:26:39 AM UTCgbrandenStatusNone=>Duplicate
      Assigned toNone=>gbranden
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1