From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Postgres Documentation List <docs@postgreSQL.org>
Cc: Postgres Hackers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Merging old man pages
Date: Sat, 17 Jul 1999 20:54:25 +0000
Message-ID: <3790ED81.B9F38C0D@alumni.caltech.edu> (raw)
References: <20015.932232121@sss.pgh.pa.us>
> OK, let me get this straight: man pages will no longer be in the CVS
> tree because they will no longer be original files, but they will be
> part of the standard distribution as derived files, right?
Yes. Well, at least, maybe, sort of...
As is the case with the other (html) docs, I'm planning on putting a
man tarball into the distribution. Up to now, the easiest way to do
that is to put the tarball into cvs, but I'm open to other
suggestions.
Do I guess correctly that we currently generate our production
releases by actually doing a cvs checkout and then a "mini-build" of
the system to generate the yacc/bison derived files? If so, we could
consider doing the same sort of thing for the html and man products,
but it (probably) makes this packaging process more fragile.
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: lockhart@alumni.caltech.edu, tgl@sss.pgh.pa.us, docs@postgreSQL.org, hackers@postgreSQL.org
Subject: Re: [HACKERS] Merging old man pages
In-Reply-To: <3790ED81.B9F38C0D@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox