From owner-freebsd-current Mon Dec 11 9: 8: 3 2000 From owner-freebsd-current@FreeBSD.ORG Mon Dec 11 09:08:01 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 4424337B402; Mon, 11 Dec 2000 09:08:01 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 6E91F89A; Mon, 11 Dec 2000 09:07:56 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id JAA16720; Mon, 11 Dec 2000 09:07:55 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A3509E9.F1D19305@cup.hp.com> Date: Mon, 11 Dec 2000 09:07:53 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <20001211094815.D96665@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > 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. This, I don't care about. We're never going to use an old groff(1) with the new files or vice versa. From a usage point of view, I don't care about the implementation, just the interface. Let me rephrase the question: Did you modify the manpages to get it to work with the new groff(1) or is the new groff(1) backward compatible with the old groff(1)? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message