public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Marc G. Fournier <[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 17:28:05 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Marc G. Fournier wrote:
> On Fri, 2 Jul 2010, 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.
> 
> that shouldn't be an issue ... Peter runs an update every 3 hours on that 
> machine right now as it is ...

OK, everyone seems to like requiring dia.  I wasn't sure how popular dia
was.  One hack solution to allow builds without dia would be to create a
Makefile rule that creates empty PNG files to match the dia files.

Can someone provide the command-line to build the PNG files from the DIA
files?

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