Date: Sat, 22 Jan 2011 10:58:25 +0100 From: Gary Jennejohn <gljennjohn@googlemail.com> To: Ulrich =?ISO-8859-1?Q?Sp=F6rlein?= <uqs@freebsd.org> Cc: stable@freebsd.org, current@freebsd.org Subject: Re: RFC vgrind in base (and buildworld) Message-ID: <20110122105825.71abfd71@ernst.jennejohn.org> In-Reply-To: <20110121222008.GB65811@acme.spoerlein.net> References: <20110120201740.GE24444@acme.spoerlein.net> <20110121222008.GB65811@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Jan 2011 23:20:09 +0100 Ulrich Spörlein <uqs@freebsd.org> 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. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110122105825.71abfd71>