public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Rafael Martinez <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Documentation and explanatory diagrams
Date: Fri, 2 Jul 2010 18:04:29 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Marc G. Fournier wrote:
> On Fri, 2 Jul 2010, Bruce Momjian wrote:
> 
> > Marc G. Fournier wrote:
> >> On Fri, 2 Jul 2010, Robert Haas wrote:
> >>
> >>> On Fri, Jul 2, 2010 at 5:28 PM, Bruce Momjian <[email protected]> wrote:
> >>>> OK, everyone seems to like requiring dia.
> >>>
> >>> I don't like it a bit.  It's hard enough for people to build the docs as
> >>> it is.
> >>
> >> Why should anyone build the docs?  Its part of the tarball process, so the
> >> only ppl that should be doing it are those coming from CVS, no ... ?
> >
> > People often built them to verify the SGML markup and to view the
> > content/markup before submitting a doc patch.
> 
> Good point ... so, part of the Makefile should be modified for a flag to 
> disable dia build?  "make NO_DIA=yes" ?  Or, maybe have it default to NO 
> and for the tarball build, I'd modify the script for building it?

I am afraid if we don't enable dia by default then we will end up with
production documentation without images.  I think we have to default dia
to on, and give a reasonable error when it doesn't exist, and mention
how to turn it off.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +

view thread (114+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation and explanatory diagrams
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox