Date: Wed, 30 Jun 2010 01:08:57 -0700 From: Garrett Cooper <gcooper@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: arch@freebsd.org Subject: Re: dwb : groff replacement proposal Message-ID: <AANLkTik2ARa6uMRRnxun7QDs9wCDYnkKFsXn8u1t-fH7@mail.gmail.com> In-Reply-To: <20100630062403.GA49395@troutmask.apl.washington.edu> References: <4C2AB793.4040601@laposte.net> <20100630034622.GA48794@troutmask.apl.washington.edu> <AANLkTikzG3lkZ4QCKcM_YBeB5MZlZVOF2Q_NVJy9Z75D@mail.gmail.com> <20100630062403.GA49395@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 29, 2010 at 11:24 PM, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > On Tue, Jun 29, 2010 at 09:48:00PM -0700, Garrett Cooper wrote: >> On Tue, Jun 29, 2010 at 8:46 PM, Steve Kargl >> <sgk@troutmask.apl.washington.edu> wrote: >> > On Wed, Jun 30, 2010 at 05:18:43AM +0200, Cyrille Lefevre wrote: >> >> >> >> seen on http://wiki.freebsd.org/ContribSoftware, groff have switch >> >> to GPLv3 license, so, >> > >> > So what? ?The version of groff in the src/ isn't >> > going to suddenly stop working. ?Please send this >> > type of email to free-advocacy or freebsd-chat. >> > It has no place here. >> >> Steve, >> =A0 =A0 I do see his point because bitrot software doesn't help, and apa= rt >> from our toolchain and a few other things, a lot of the GNU software >> is being forced out eventually. groff hasn't been touched in ages >> however. > > "groff hasn't been touched in ages" so FreeBSD suddenly can't > render its man pages? > > Cyrille's post should have gone to freebsd-advocacy or -chat. > The fact that FSF is moving its software distributions to > GPLv3 isn't some state secret. > >> =A0 =A0 Regardless, there's already work being done to remedy this in th= e >> FreeBSD community; see: >> http://www.freebsdnews.net/2009/05/11/deprecating-groff-bsd-manual-displ= ay/ >> for one link. > > I'm aware of mdocml and other efforts. =A0None of these efforts > come close to replacing the functionality provided by the > version of groff in src/. =A0The current version of groff in > FreeBSD meets FreeBSD needs. =A0Do you envision bitrot in > FreeBSD's groff that will go unnotice? =A0Do you envision an > in flux of man pages into FreeBSD that are written in > mdoc (or other macro packages) that can't be rendered by > FreeBSD's version of groff, but can be rendered by mdocml? Well, ok. The reply was to kind of make the Cyrille message moot, but it kind of morphed into something else by accident. I think we should bury the hatchet on this topic after this to avoid useless spinning. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik2ARa6uMRRnxun7QDs9wCDYnkKFsXn8u1t-fH7>