public inbox for [email protected]  

help / color / mirror / Atom feed

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

Tom Lane wrote:
> Alvaro Herrera <[email protected]> writes:
> > Excerpts from Peter Eisentraut's message of jue jul 01 21:52:00 -0400 2010:
> >> Is there something that makes installing dia more challenging than the
> >> other documentation build tools?
> 
> > Err, I dunno -- it's just an apt-get away for me, but what will Tom say
> > when it doesn't work on his ancient HP-UX 10.20 system?
> 
> I don't try to build the docs on that box anyway --- it does have
> openjade but such an old version that they don't build.  In practice
> building the docs already takes much more modern infrastructure than
> compiling the source code; and besides there are many fewer people
> who care about doing it.
> 
> A more interesting question is whether Marc can install a working
> version of dia on whatever he uses to wrap the tarballs.

One more issue is that the dia and png files are going to impact our
download sizes:

	526k     ./dia
	483k     ./png

If we generate the png from the dia files, we are looking at increasing
the source download by 526k and the binary downloads by 483k for all
existing images and, of course, as we add images, these sizes will
increase.

-- 
  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]
  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