Date: Thu, 20 Jan 2011 23:11:43 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@FreeBSD.org> To: Alexander Kabaev <kabaev@gmail.com> Cc: stable@FreeBSD.org, current@FreeBSD.org Subject: Re: RFC vgrind in base (and buildworld) Message-ID: <20110120221142.GA65811@acme.spoerlein.net> In-Reply-To: <20110120153103.50a86ad3@kan.dnsalias.net> References: <20110120201740.GE24444@acme.spoerlein.net> <20110120153103.50a86ad3@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, 20.01.2011 at 15:31:03 -0500, Alexander Kabaev wrote:
> On Thu, 20 Jan 2011 21:17:40 +0100
> Ulrich Sp=C3=B6rlein <uqs@FreeBSD.org> wrote:
>=20
> > Hello,
> >=20
> > 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.
> >=20
> > 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.
> >=20
> > OTOH, there are much more useful tools to vgrind(1) for source code
> > formatting. So do we still have vgrind(1) users out there?
> >=20
> > Regards,
> > Uli
>=20
> Why it needs to be in bootsrap tools at all? We have build tools for
> this exact purpose.
Because the legacy target has the nice semantics of calling a tool's
obj,depend,all,install targets instead of doing only `all' or
`build-tool'.
We also currently set GROFF_BIN_PATH, GROFF_FONT_PATH, and
GROFF_TMAC_PATH to point to ${WORLDTMP}/legacy/... so it was trivial to
get groff working that way. I don't know the history of why we actually
do this for groff (it is broken currently), therefore I simply
piggy-backed onto that solution.
I forgot the link earlier:
https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/log/?h=3Dgroff
I wish there was an easy way to cleanly have this as a build-tool. While
we're at it: strfile similarly should be moved to a build-tool, not a
bootstrap-tool, as it is also only used to as a pre-requisite to
building fortune(6).
If someone can come up with a policy of what should go where, I'll
happily try to shoehorn the groff/vgrind/strfile things into it ...
Uli
--IS0zKkzwUGydFO0o
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iQEcBAEBAgAGBQJNOLMeAAoJEKOmmGRKr4LOMIQH/1N/PJFy4g/+8+pTIX5MNUiF
7Pt/+cZ3i1tkJBokiMquzmUjE1+8cl2hzoSWadR7K1hl8k7OAsbUGcpmZxhh9ZBH
nb96mEYXBilqakR7aSPKIfwH6koGWX8nm/fmEJDcxF7+7wsXufMZyit153mfnqIa
alQcmIMbdFcKM9twZFQwsf5CPwuiPh7YTfto8NOBO8OgFw/NAZriuxjWHrNEbrc9
H+JdCrU44412ROMW1fQ0ySD0Pkt4QBynofycpj7bM1eLhU+UljSbdMnXqzGE4CKe
NwTOhhU/CFvbILYxzlnKS2eUCVT3/JXVO2/ie0u23RYAfUurQ77geDPPrVvf4+c=
=saFF
-----END PGP SIGNATURE-----
--IS0zKkzwUGydFO0o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110120221142.GA65811>