[bug #57630] test-groff clobbers environment's GROFF_*_PATH variables

[G. Branden Robinson]

Update of bug #57630 (project groff):

                  Status:               Need Info => Wont Fix               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #10:

After four months without discussion, I'm closing this one for now.  I don't
think test-groff is intended for use like a real system executable; mainly it
drives the regression tests, as Ingo noted.

But that's not all I use it for.

I also have some shell aliases 'tg' and 'tgu' (the latter adding the -Tutf8
parameter) which I run _all the time_ from my groff git checkout.  I can't
even count how many experiments I've conducted this way, using a build tree's
groff as a kind of REPL.


$ alias tg tgu
alias tg='./build/test-groff'
alias tgu='./build/test-groff -Tutf8'


I recommend that close observers of (and participants in!) groff development
do something similar.

I'm a bit way of changing test-groff such that it operates in a fused
installation/build environment, something is never seen in any other
circumstance.

If someone wants to use such a thing as a means of uncovering possible bugs,
then I advise copying the script to their $HOME/bin or similar and making the
changes documented earlier in this bug's discussion.  And then, if problems
turn up, trying to construct a minimal reproducer script to get at the
misbehavior.

I'm therefore resolving this bug as wontfix, without prejudice, to use a U.S.
legal metaphor.

    _______________________________________________________

Reply to this item at:

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

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