From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 18:15:18 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1248B106566B; Sat, 22 Jan 2011 18:15:18 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id E6CA08FC13; Sat, 22 Jan 2011 18:15:17 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id p0MIFHRB030932; Sat, 22 Jan 2011 10:15:17 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id p0MIFHho030931; Sat, 22 Jan 2011 10:15:17 -0800 (PST) (envelope-from sgk) Date: Sat, 22 Jan 2011 10:15:17 -0800 From: Steve Kargl To: Gary Jennejohn Message-ID: <20110122181517.GA30908@troutmask.apl.washington.edu> References: <20110120201740.GE24444@acme.spoerlein.net> <20110121222008.GB65811@acme.spoerlein.net> <20110122105825.71abfd71@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110122105825.71abfd71@ernst.jennejohn.org> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, current@freebsd.org, Ulrich Sp?rlein Subject: Re: RFC vgrind in base (and buildworld) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2011 18:15:18 -0000 On Sat, Jan 22, 2011 at 10:58:25AM +0100, Gary Jennejohn wrote: > On Fri, 21 Jan 2011 23:20:09 +0100 > Ulrich Sp?rlein wrote: > > > On Thu, 20.01.2011 at 21:17:40 +0100, Ulrich Sp?rlein wrote: > > > Hello, > > > > > > Currently our buildworld relies on groff(1) and vgrind(1) being present > > > in the host system. I have a patch ready that at least makes sure these > > > are built during bootstrap-tools and completes the WITHOUT_GROFF flag. > > > > > > vgrind(1) is only used for two papers under share/doc and we could > > > easily expand the results and commit them to svn directly, alleviating > > > the need to run vgrind(1) during buildworld. > > > > > > OTOH, there are much more useful tools to vgrind(1) for source code > > > formatting. So do we still have vgrind(1) users out there? > > > > > > Regards, > > > Uli > > > > [trying to get this thread back on track] > > > > Does anyone actually care about vgrind in base? Will people be angry if > > I unroll the 2 cases where it is used under share/doc? > > > > I personally have never used vgrind, but since it's available as part of > /usr/ports/textproc/heirloom-doctools IMO it would be safe to remove it > from base, maybe with a note in UPDATING. AFAICT, heirloom-doctools does not work on 64-bit platforms. vgrind may be ok but nroff and troff die rather quickly with a segfault when it tries to use a macro package such as mdoc. -- Steve