Date: Tue, 25 May 2010 09:52:31 -0700 From: Julian Elischer <julian@elischer.org> To: Eitan Adler <lists@eitanadler.com> Cc: Ben Fiedler <bfiedler@asu.edu>, "Julian H. Stacey" <jhs@berklix.com>, hackers@freebsd.org Subject: Re: GSoC: BSD text tools Message-ID: <4BFC004F.1090101@elischer.org> In-Reply-To: <AANLkTikz2m7LS0DC4i7tKFSHQIyZuCKSxiHWlyTHClhs@mail.gmail.com> References: <AANLkTik90k1HlsDJsIgRhCnAcU8_ympR15ZJcoL07A5m@mail.gmail.com> <201005251450.o4PEo9tF099503@fire.js.berklix.net> <AANLkTikz2m7LS0DC4i7tKFSHQIyZuCKSxiHWlyTHClhs@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/25/10 8:33 AM, Eitan Adler wrote: >> No. Do not remove groff or associated tools from /usr/src ! >> Roff has been in Unix /usr/src since '77 or earlier. >> A lot of people use tools from that descendancy as production tools. > > So? If it isn't a very commonly used tool and isn't necessary for 99% > of cases I don't seem the harm of removing it from base and making it > a port? BSD has always been ab;e to produce it's documentation as part of its build Please keep this true. > >> >> However if you just mean >> "I'll be working on getting man to call XYZ rather than groff" >> then I have no comment. > > -- > Eitan Adler > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFC004F.1090101>