From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsqlrpms-hackers(at)pgfoundry(dot)org, Tino Wildenhain <tino(at)wildenhain(dot)de>, Andre Truter <linux(at)trusoft(dot)co(dot)za>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Supplemental contrib docs (was: [GENERAL] DBlink documentation) |
Date: | 2006-01-04 00:20:38 |
Message-ID: | 43BB14D6.8000803@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-01-04 02:12:29 | Re: CONSTRAINT syntax in ALTER TABLE |
Previous Message | Tom Lane | 2006-01-03 23:56:37 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |
From | Date | Subject | |
---|---|---|---|
Next Message | Allen Fair | 2006-01-04 01:06:50 | Re: Moving Tablespaces |
Previous Message | Tom Lane | 2006-01-03 23:56:37 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |