From owner-freebsd-current Tue Dec 12 9:44: 4 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 12 09:44:02 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 774E137B402; Tue, 12 Dec 2000 09:43:53 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id C51D338C; Tue, 12 Dec 2000 09:43:52 -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 JAA26767; Tue, 12 Dec 2000 09:43:52 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A3663DB.2DA71F0E@cup.hp.com> Date: Tue, 12 Dec 2000 09:43:55 -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> <3A3509E9.F1D19305@cup.hp.com> <20001212102344.B92312@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: > > > 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)? > > > The new groff(1) is not always backwards compatible. Ok, thanks. That's all I wanted to hear. > OK, I will augment the USRDIRS then, add the groff to bootstrap-tools, > and leave the better (if one exists) implementation to someone else. Works for me. thanks, -- 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