Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.groff.bug > #1748
| From | "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> |
|---|---|
| Newsgroups | gnu.groff.bug |
| Subject | [bug #57630] test-groff clobbers environment's GROFF_*_PATH variables |
| Date | 2020-02-13 05:45 -0500 |
| Message-ID | <mailman.779.1581590726.2412.bug-groff@gnu.org> (permalink) |
| References | (3 earlier) <20200119-145610.sv93119.40026@savannah.gnu.org> <20200120-012155.sv93188.90981@savannah.gnu.org> <20200120-050503.sv93119.89975@savannah.gnu.org> <20200124-215722.sv93188.63007@savannah.gnu.org> <20200213-104522.sv108747.23866@savannah.gnu.org> |
Update of bug #57630 (project groff):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #7:
It seems like we don't really have a consensus on this one yet.
Maybe we need an actual definition of what it is 'test-groff' is actually
supposed to do.
Ersatz user-local-packaging of the built groff tree as a runtime?
Ersatz isolated containerization of the built groff tree as a runtime?
These objectives are in tension.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57630>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Back to gnu.groff.bug | Previous | Next | Find similar | Unroll thread
[bug #57630] test-groff clobbers environment's GROFF_*_PATH variables "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> - 2020-02-13 05:45 -0500
csiph-web