public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Conway <[email protected]>
To: [email protected]
Cc: Tino Wildenhain <[email protected]>
Cc: [email protected]
Cc: Andre Truter <[email protected]>
Subject: Re: [Pgsqlrpms-hackers] Re: DBlink documentation
Date: Sat, 17 Dec 2005 12:17:50 -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]>

Tom Lane wrote:
> 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).

Well, in my own defense, I pointed out the change explicitly when I 
submitted the patch (which was over 3 years ago now, prior to 7.3 beta 
feature freeze), and no one objected back then:
   http://archives.postgresql.org/pgsql-patches/2002-08/msg00640.php

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

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.

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