From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | pgsqlrpms-hackers(at)pgfoundry(dot)org, Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-general(at)postgresql(dot)org, Andre Truter <linux(at)trusoft(dot)co(dot)za> |
Subject: | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |
Date: | 2005-12-17 20:47:54 |
Message-ID: | 9980.1134852474@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Joe Conway <mail(at)joeconway(dot)com> 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?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-17 21:10:25 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |
Previous Message | Joe Conway | 2005-12-17 20:17:50 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-17 21:10:25 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |
Previous Message | Joe Conway | 2005-12-17 20:17:50 | Re: [Pgsqlrpms-hackers] Re: DBlink documentation |