Date: Tue, 8 Feb 2000 09:23:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: jeffw AT darwin DOT sfbr DOT org, djgpp-workers AT delorie DOT com
Subject: Re: second Bash 2.03 r.c. available
In-Reply-To: <200002072049.PAA07527@delorie.com>
Message-ID: <Pine.SUN.3.91.1000208092245.28790C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 7 Feb 2000, Mark E. wrote:

> > [1] How about distributing formatted man pages in `man/cat1' instead
> > of unformatted pages in `man/man1' ?  Unformatted ones would be more
> > appropriate for the .s archive.
> 
> I put them in man/man1 because that's where 'make install' puts them. 
> I don't know much about where man pages should go, so I'll also send 
> this to djgpp-workers and ask the same question.

I can only share my experience.  What I usually do is to run Groff
(manually) on the unformatted man pages, like this:

	   groff -man man/man1/foo.1 > man\cat1\foo.1

(this can be made less painful by writing a suitable batch file or
shell script).  Then I include only the formatted pages in the binary
zips.

I think it's too much to require a user to install Groff just to read
the docs, because Groff is a large package.