Re: [groff] [Groff] Next release - maintainership

Hi Dave, Dave Kemper wrote on Wed, Feb 21, 2018 at 06:18:40PM -0500: > On 2/21/18, Ingo Schwarze wrote: >> You can hardly use *roff without >> macros (well, there are rumours about a few people using their very >> own, personal macro sets, but that's certainly the exception

Re: [groff] [Groff] Next release - maintainership

Thanks, Ingo. You make some good points. A few responses inlined below. On 2/21/18, Ingo Schwarze wrote: > Dave Kemper wrote on Wed, Feb 21, 2018 at 02:26:15PM -0500: > >> Does it make any sense to split groff into two packages: one that is >> just the base groff system, and

Re: [groff] [Groff] Next release - maintainership

Hi, Dave Kemper wrote on Wed, Feb 21, 2018 at 02:26:15PM -0500: > Does it make any sense to split groff into two packages: one that is > just the base groff system, and one that is just the macro sets? I don't think it makes much sense. You can hardly use *roff without macros (well, there are

Re: [groff] [Groff] Next release - maintainership

Catching up with some old groff-list email: On 9/16/17, Bertrand Garrigues wrote: > I can take in charge part of the job of the maintainer: the build > system, making release; I've also studied src/roff/troff source code and > I'm planning to propose changes in