public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Tino Wildenhain <[email protected]>
Cc: Andre Truter <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: DBlink documentation
Date: Sat, 17 Dec 2005 13:31:08 -0500
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]>

Tino Wildenhain <[email protected]> writes:
> Am Samstag, den 17.12.2005, 16:53 +0200 schrieb Andre Truter:
>> I would be nice if the documentation could be online though, then I
>> would not need to download the whole postgres source just to get the
>> documentation for one small part.

> This is understandable ;) But in this case not postgres peoples
> fault. There is no reason a package manager should exclude parts
> of the software at will.

Actually, I don't think you can reasonably blame the Debian packager
for having overlooked the fact that contrib/dblink has more
documentation files besides its README.  The PGDG RPM people overlooked
that too, as did Red Hat (ie, me).

Now that I look, tsearch2 has also adopted a nonstandard documentation
layout.

While we (the packagers) could fix this now that our attention has been
called to it, I wonder whether the better plan wouldn't be to insist
that dblink and tsearch2 fall into line with the rest of the contrib
modules.  At the very least we need a uniform convention for docs files
so that packagers won't be playing catchup forever.

			regards, tom lane

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: 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