From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:20:11 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 0805C106566B; Fri, 21 Jan 2011 22:20:11 +0000 (UTC) (envelope-from uqs@freebsd.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 95E3B8FC16; Fri, 21 Jan 2011 22:20:10 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.4/8.14.4) with ESMTP id p0LMK9X1098497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2011 23:20:09 +0100 (CET) (envelope-from uqs@freebsd.org) Date: Fri, 21 Jan 2011 23:20:09 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: current@freebsd.org, stable@freebsd.org Message-ID: <20110121222008.GB65811@acme.spoerlein.net> Mail-Followup-To: current@FreeBSD.org, stable@FreeBSD.org References: <20110120201740.GE24444@acme.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20110120201740.GE24444@acme.spoerlein.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 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: Fri, 21 Jan 2011 22:20:11 -0000 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? Regards, Uli