On Sat, Dec 09, 2000 at 12:29:54PM -0800, Marcel Moolenaar wrote:
> Ruslan Ermilov wrote:
> >
> > On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote:
> > > Ruslan Ermilov wrote:
> > > >
> > > > The attached patches (p4 and p5) try to solve this bootstrapping
> > > > problem with groff(1).
> > >
> > > Sorry, I missed this statement before. What exactly are the
> > > bootstrapping problems you're seeing?
> > >
> > New groff(1) provides new versions of macro packages and device
> > files. When building, we should use THEM rather than installed
> > (obsolete) ones.
>
> Is the old groff(1) incompatible with the new groff(1) in the sense that
> manpages created with the old groff(1) are visibly different from the
> manpages created with the new groff(1)?
>
Once again. groff(1) supplies macro packages and device description
files. New groff is likely to provide modified files. The typical
build system uses groff(1) to build documentation (unless you have
NO_SHAREDOCS defined). If, additionally, one has MANBUILDCAT set
to some value, ``make world'' will build and install preformatted
manual pages. So the answer to your question is: yes for BSD docs,
and "probably" for manual pages.
--
Ruslan Ermilov Oracle Developer/DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
