public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joe Conway <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Cc: Tino Wildenhain <[email protected]>
Cc: [email protected]
Cc: Andre Truter <[email protected]>
Subject: Re: [Pgsqlrpms-hackers] Re: DBlink documentation
Date: Tue, 03 Jan 2006 15:52:24 -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]>
Tom Lane wrote:
> Joe Conway <[email protected]> writes:
>
>>I'm happy to lump all the docs back into the README if that's what you
>>want, but I split it up in the first place because it was getting very long.
>
> No, I'm not really proposing that we force all contrib modules to have
> only a README. I'm just annoyed by the lack of consistency (dblink/doc
> versus tsearch2/docs, and some of the other modules seem to have some
> doc files just loose in their top directory).
>
> 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?
Thanks,
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], [email protected]
Subject: Re: [Pgsqlrpms-hackers] Re: 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