Re: Documentation tree (again)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Postgres Documentation List <docs(at)postgresql(dot)org>, Postgres Hackers List <hackers(at)postgresql(dot)org>
Subject: Re: Documentation tree (again)
Date: 1998-02-26 21:41:14
Message-ID: Pine.BSF.3.96.980226174001.230I-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 26 Feb 1998, Thomas G. Lockhart wrote:

> OK, so when I asked earlier about documentation directory structure,
> Marc indicated that we should put things into a separate area, not just
> plop them into the usual src/ tree. I agree, but am not sure _where_ to
> actually put them.
>
> I am thinking of making a directory doc/src/sgml (under the existing doc
> directory) which would contain the sgml source code. doc/src would
> contain that and a Makefile which would know how to invoke the Makefile
> in doc/src/sgml. A "make install" from doc/src would copy gzip packaged
> files up to doc/, where they would be for a distribution.
>
> A Makefile in doc/ would unpack the gzip tar files of html into
> directories right under doc/, such as doc/tutorial, doc/userguide, etc.
>
> Is this OK? Some questions:

Sounds good to me...

> 1) Should all html be isolated into subdirectories under a doc/html/
> directory?

I'd say that all html should be installed in $prefix/html when a
'make install' is issued. You should be able to remove the package after
installing...

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-02-26 21:43:40 Re: [HACKERS] mode of libs
Previous Message The Hermit Hacker 1998-02-26 21:38:27 Re: [HACKERS] SELECT currval('SEQ') broken?