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
On Thu, 20 Jan 2011 21:17:40 +0100 Ulrich Sp?rlein <uqs@FreeBSD.org> 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, > UliWhy it needs to be in bootsrap tools at all? We have build tools for this exact purpose. -- Alexander Kabaev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20110120/8f867827/signature.pgp
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
Damien Fleuriot wrote:> 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.Anyways, there is also a reasonable number of people who know what vgrind is about: pretty printing various source codes through troff particularly C code. Another tool doing the same through TeX is tgrind.> The less clutter, the better :)Except perhaps not two people have the same idea of "clutter". For example many people think that half of the content of the so-called "base system" is clutter. -- Michel TALON