From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 13:07:57 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BDD1106564A for ; Sun, 23 Jan 2011 13:07:57 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3B16B8FC0C for ; Sun, 23 Jan 2011 13:07:55 +0000 (UTC) Received: by wwf26 with SMTP id 26so3116743wwf.31 for ; Sun, 23 Jan 2011 05:07:54 -0800 (PST) Received: by 10.227.132.70 with SMTP id a6mr3067356wbt.193.1295788074371; Sun, 23 Jan 2011 05:07:54 -0800 (PST) Received: from dfleuriot.local (did75-17-88-165-130-96.fbx.proxad.net [88.165.130.96]) by mx.google.com with ESMTPS id f35sm8466702wbf.8.2011.01.23.05.07.52 (version=SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 05:07:53 -0800 (PST) Message-ID: <4D3C2827.2000704@my.gd> Date: Sun, 23 Jan 2011 14:07:51 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: uqs@freebsd.org References: <20110120201740.GE24444@acme.spoerlein.net> <20110121222008.GB65811@acme.spoerlein.net> In-Reply-To: <20110121222008.GB65811@acme.spoerlein.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: RFC vgrind in base (and buildworld) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 13:07:57 -0000 On 1/21/11 11:20 PM, 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? > > Regards, > Uli > Hi Ulrich, I think I'm speaking for a reasonable amount of people when I say: I have no idea what vgrind is used for to begin with. If you can safely and easily get us rid of a binary that's only used for 2 small things when building the world, I'm all for it. The less clutter, the better :) Regards, -- Dam