public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Conway <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Cc: Tino Wildenhain <[email protected]>
Cc: Andre Truter <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Supplemental contrib docs (was: [GENERAL] DBlink documentation)
Date: Tue, 03 Jan 2006 16:20:38 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Tom Lane wrote:
> Joe Conway <[email protected]> writes:
>>Tom Lane wrote:
>>
>>>It's not only the downstream packagers that have missed these: the
>>>Makefiles don't install them either.
>>>
>>>It'd be a good idea to settle on what we want the installed file layout
>>>to be --- do we need to create subdirectories under {prefix}/doc to
>>>forestall name conflicts?
> 
>>While I'm messing with dblink, did you want me to do anything WRT this?
> 
> I don't think we settled on what we want to do yet.  Any thoughts?
> 
> I'm kind of leaning toward the subdirectory idea myself...

(I removed GENERAL, and added DOCS to the distribution of this thread)

Well I like {prefix}/doc given that's how dblink is already set up ;-)

Questions:
   - Do we want a naming convention for the files in
     {prefix}/doc?
   - Do we pre-create {prefix}/doc for every contrib
     directory in advance?

I think the answers are no, and yes, but I don't feel strongly about either.

Joe

view thread (25+ 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]
  Subject: Re: Supplemental contrib docs (was: [GENERAL] DBlink documentation)
  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