public inbox for [email protected]help / color / mirror / Atom feed
DBlink documentation 25+ messages / 11 participants [nested] [flat]
* DBlink documentation @ 2005-12-17 12:53 Andre Truter <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Andre Truter @ 2005-12-17 12:53 UTC (permalink / raw) To: [email protected] Where do I find documentation for using dblink? I am running PostgreSQL 8.03 on SuSE 9.3 and I installed the postgresql-contrib package, but it only includes the README for dblink, which only lists the functions, but it does not include any information on how to use it. For instance, it would list: dblink_connect(text) RETURNS text. But what should 'text' be? I searched through the Postgres site and mailing list archives and I get a lot of references of "look in the dblink documentation". Unfortunately I have have not yet been able to find this documentation? Can anybody please give me a link to the documentation? Thanks -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 13:20 Leonel Nunez <[email protected]> parent: Andre Truter <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Leonel Nunez @ 2005-12-17 13:20 UTC (permalink / raw) To: Andre Truter <[email protected]>; +Cc: [email protected] Andre Truter wrote: >Where do I find documentation for using dblink? > >I am running PostgreSQL 8.03 on SuSE 9.3 and I installed the >postgresql-contrib package, but it only includes the README for dblink, >which only lists the functions, but it does not include any information >on how to use it. > >For instance, it would list: > >dblink_connect(text) RETURNS text. > >But what should 'text' be? > >I searched through the Postgres site and mailing list archives and I get >a lot of references of "look in the dblink documentation". >Unfortunately I have have not yet been able to find this documentation? > >Can anybody please give me a link to the documentation? > >Thanks > > It's on the contrib package or in the contrib dir if you installed from source leonel ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 13:44 Andre Truter <[email protected]> parent: Leonel Nunez <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Andre Truter @ 2005-12-17 13:44 UTC (permalink / raw) To: [email protected] On Sat, 2005-12-17 at 06:20 -0700, Leonel Nunez wrote: > > It's on the contrib package No, unfortunately the SUSE people did not include it in the contrib package. > or in the contrib dir if you installed from source > Installed from rpm package. I have searched for the dblink source to get the docs from there, but I have also failed to find it so far. Maybe I am searching wrong? I searched the Postgres site for 'dblink source' -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ "Oh Bother!" said the Borg, "We assimilated the Pooh!" ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:04 Leonel Nunez <[email protected]> parent: Andre Truter <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Leonel Nunez @ 2005-12-17 14:04 UTC (permalink / raw) To: Andre Truter <[email protected]>; +Cc: [email protected] Andre Truter wrote: >On Sat, 2005-12-17 at 06:20 -0700, Leonel Nunez wrote: > > > >>It's on the contrib package >> >> > >No, unfortunately the SUSE people did not include it in the contrib >package. > > > >>or in the contrib dir if you installed from source >> >> >> >Installed from rpm package. >I have searched for the dblink source to get the docs from there, but I >have also failed to find it so far. >Maybe I am searching wrong? > >I searched the Postgres site for 'dblink source' > > > download the source for your PostgreSQL version unpackit and check on the contrib/dblink dir leonel ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:14 Andre Truter <[email protected]> parent: Leonel Nunez <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Andre Truter @ 2005-12-17 14:14 UTC (permalink / raw) To: Leonel Nunez <[email protected]>; +Cc: [email protected] On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote: > download the source for your PostgreSQL version unpackit > and check on the contrib/dblink dir > Yes, that is what I have been trying to do, but where do I download the dblink source from? -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:21 Douglas McNaught <[email protected]> parent: Andre Truter <[email protected]> 0 siblings, 2 replies; 25+ messages in thread From: Douglas McNaught @ 2005-12-17 14:21 UTC (permalink / raw) To: Andre Truter <[email protected]>; +Cc: Leonel Nunez <[email protected]>; [email protected] Andre Truter <[email protected]> writes: > On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote: > >> download the source for your PostgreSQL version unpackit >> and check on the contrib/dblink dir >> > > Yes, that is what I have been trying to do, but where do I download the > dblink source from? That's what he's trying to tell you--it's in the 'contrib' directory of the main source tarball. -Doug ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:33 Russ Brown <[email protected]> parent: Douglas McNaught <[email protected]> 1 sibling, 3 replies; 25+ messages in thread From: Russ Brown @ 2005-12-17 14:33 UTC (permalink / raw) To: [email protected] On Sat, 17 Dec 2005 08:21:29 -0600, Douglas McNaught <[email protected]> wrote: > Andre Truter <[email protected]> writes: > >> On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote: >> >>> download the source for your PostgreSQL version unpackit >>> and check on the contrib/dblink dir >>> >> >> Yes, that is what I have been trying to do, but where do I download the >> dblink source from? > > That's what he's trying to tell you--it's in the 'contrib' directory > of the main source tarball. > Is the documentation not available online somewhere? -- Russ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:37 Douglas McNaught <[email protected]> parent: Russ Brown <[email protected]> 2 siblings, 0 replies; 25+ messages in thread From: Douglas McNaught @ 2005-12-17 14:37 UTC (permalink / raw) To: Russ Brown <[email protected]>; +Cc: [email protected] "Russ Brown" <[email protected]> writes: > Is the documentation not available online somewhere? For the stuff in 'contrib', I don't think so. Might be a good project for someone. :) -Doug ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:53 Andre Truter <[email protected]> parent: Douglas McNaught <[email protected]> 1 sibling, 1 reply; 25+ messages in thread From: Andre Truter @ 2005-12-17 14:53 UTC (permalink / raw) To: Douglas McNaught <[email protected]>; +Cc: Leonel Nunez <[email protected]>; [email protected] On Sat, 2005-12-17 at 09:21 -0500, Douglas McNaught wrote: > Andre Truter <[email protected]> writes: > > > On Sat, 2005-12-17 at 07:04 -0700, Leonel Nunez wrote: > > > >> download the source for your PostgreSQL version unpackit > >> and check on the contrib/dblink dir > >> > > > > Yes, that is what I have been trying to do, but where do I download the > > dblink source from? > > That's what he's trying to tell you--it's in the 'contrib' directory > of the main source tarball. > Ah! I misunderstood. I expected the dblink or contrib stuff to be a separate project, not part of the postgres source tree. That explain why I could not find it. Thanks, I'll download the Posgres source then. 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. Or, is there a CVS browser available, so I can only checkout/download the dblink stuff? (Bandwidth is a problem for me at the moment) -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ "Oh Bother!" said the Borg, "We assimilated the Pooh!" ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 14:53 Greg Sabino Mullane <[email protected]> parent: Russ Brown <[email protected]> 2 siblings, 1 reply; 25+ messages in thread From: Greg Sabino Mullane @ 2005-12-17 14:53 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Is the documentation not available online somewhere? Quick version for you: http://www.gtsm.com/dblink/ - -- Greg Sabino Mullane [email protected] PGP Key: 0x14964AC8 200512170951 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFDpCYXvJuQZxSWSsgRAgGtAKDk9H/KFCjNjdaxGaPQkqdYzLITwACglSQt cG2yNm8kVfsiqE4DcPVZOpQ= =9YZG -----END PGP SIGNATURE----- ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 16:03 Andre Truter <[email protected]> parent: Greg Sabino Mullane <[email protected]> 0 siblings, 0 replies; 25+ messages in thread From: Andre Truter @ 2005-12-17 16:03 UTC (permalink / raw) To: Greg Sabino Mullane <[email protected]>; +Cc: [email protected]; [email protected] On Sat, 2005-12-17 at 14:53 +0000, Greg Sabino Mullane wrote: > > Is the documentation not available online somewhere? > > Quick version for you: > > http://www.gtsm.com/dblink/ > > Great! This is exactly what I want. Thanks Greg! -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 16:09 Tino Wildenhain <[email protected]> parent: Andre Truter <[email protected]> 0 siblings, 2 replies; 25+ messages in thread From: Tino Wildenhain @ 2005-12-17 16:09 UTC (permalink / raw) To: Andre Truter <[email protected]>; +Cc: Douglas McNaught <[email protected]>; Leonel Nunez <[email protected]>; [email protected] Am Samstag, den 17.12.2005, 16:53 +0200 schrieb Andre Truter: ... > Thanks, I'll download the Posgres source then. > > 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. The complete software includes all you need. Well done packages either have a big package of all or single packages you install which include the documentation too. If someone does not use a package, (s)he is downloading the source anyway to get postgres :-) Regards Tino ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 18:02 Andre Truter <[email protected]> parent: Tino Wildenhain <[email protected]> 1 sibling, 0 replies; 25+ messages in thread From: Andre Truter @ 2005-12-17 18:02 UTC (permalink / raw) To: [email protected] On Sat, 2005-12-17 at 17:09 +0100, Tino Wildenhain wrote: > > This is understandable ;) But in this case not postgres peoples > fault. Yes, I realise it is not the fault of the postgres people and I did not intend to make it sound like that. I am a bit disappointed that the rpm package that comes with SuSE does not include all the docs. I will mention this on the SuSE mailing list. -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ "Oh Bother!" said the Borg, "We assimilated the Pooh!" ~ ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-17 18:31 Tom Lane <[email protected]> parent: Tino Wildenhain <[email protected]> 1 sibling, 1 reply; 25+ messages in thread From: Tom Lane @ 2005-12-17 18:31 UTC (permalink / raw) To: Tino Wildenhain <[email protected]>; +Cc: Andre Truter <[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 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2005-12-17 20:17 Joe Conway <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Joe Conway @ 2005-12-17 20:17 UTC (permalink / raw) To: [email protected]; +Cc: Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[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 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2005-12-17 20:47 Tom Lane <[email protected]> parent: Joe Conway <[email protected]> 0 siblings, 3 replies; 25+ messages in thread From: Tom Lane @ 2005-12-17 20:47 UTC (permalink / raw) To: Joe Conway <[email protected]>; +Cc: [email protected]; Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[email protected]> 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? regards, tom lane ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2005-12-17 21:10 Bruce Momjian <[email protected]> parent: Tom Lane <[email protected]> 2 siblings, 0 replies; 25+ messages in thread From: Bruce Momjian @ 2005-12-17 21:10 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Joe Conway <[email protected]>; [email protected]; Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[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? I personally never saw those doc/ files when I was modifying dblink. I had to grope around in the regression tests to see how the functions worked. -- Bruce Momjian | http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: DBlink documentation @ 2005-12-18 04:35 Karl O. Pinc <[email protected]> parent: Russ Brown <[email protected]> 2 siblings, 0 replies; 25+ messages in thread From: Karl O. Pinc @ 2005-12-18 04:35 UTC (permalink / raw) To: Russ Brown <[email protected]>; +Cc: [email protected]; Andre Truter <[email protected]> On 12/17/2005 08:33:02 AM, Russ Brown wrote: > Is the documentation not available online somewhere? There is always the CVS web interface: http://developer.postgresql.org/cvsweb.cgi/pgsql/ Karl <[email protected]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2005-12-19 21:55 Jim C. Nasby <[email protected]> parent: Tom Lane <[email protected]> 2 siblings, 0 replies; 25+ messages in thread From: Jim C. Nasby @ 2005-12-19 21:55 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Joe Conway <[email protected]>; [email protected]; Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[email protected]> On Sat, Dec 17, 2005 at 03:47:54PM -0500, Tom Lane wrote: > 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? README is probably fine for most of what's in contrib, but for other stuff we should support a doc directory. tsearch2 currently has 100k of HTML in docs, I really don't think we want to cram all that into the README. -- Jim C. Nasby, Sr. Engineering Consultant [email protected] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2006-01-03 23:52 Joe Conway <[email protected]> parent: Tom Lane <[email protected]> 2 siblings, 1 reply; 25+ messages in thread From: Joe Conway @ 2006-01-03 23:52 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected]; Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[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 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: [Pgsqlrpms-hackers] Re: DBlink documentation @ 2006-01-03 23:56 Tom Lane <[email protected]> parent: Joe Conway <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Tom Lane @ 2006-01-03 23:56 UTC (permalink / raw) To: Joe Conway <[email protected]>; +Cc: [email protected]; Tino Wildenhain <[email protected]>; [email protected]; Andre Truter <[email protected]> Joe Conway <[email protected]> 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... regards, tom lane ^ permalink raw reply [nested|flat] 25+ messages in thread
* Supplemental contrib docs (was: [GENERAL] DBlink documentation) @ 2006-01-04 00:20 Joe Conway <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Joe Conway @ 2006-01-04 00:20 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected]; Tino Wildenhain <[email protected]>; Andre Truter <[email protected]>; pgsql-docs Tom Lane wrote: > Joe Conway <[email protected]> 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 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Supplemental contrib docs (was: [GENERAL] DBlink documentation) @ 2006-01-04 02:19 Jim C. Nasby <[email protected]> parent: Joe Conway <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Jim C. Nasby @ 2006-01-04 02:19 UTC (permalink / raw) To: Joe Conway <[email protected]>; +Cc: Tom Lane <[email protected]>; [email protected]; Tino Wildenhain <[email protected]>; Andre Truter <[email protected]>; pgsql-docs On Tue, Jan 03, 2006 at 04:20:38PM -0800, Joe Conway wrote: > Tom Lane wrote: > >Joe Conway <[email protected]> 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. By {prefix} do you mean where PostgreSQL is being installed? If so, that would be highly non-standard. I think what you'd want is {prefix}/share/doc/postgresql/contrib/. -- Jim C. Nasby, Sr. Engineering Consultant [email protected] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Supplemental contrib docs @ 2006-01-04 04:19 Joe Conway <[email protected]> parent: Jim C. Nasby <[email protected]> 0 siblings, 1 reply; 25+ messages in thread From: Joe Conway @ 2006-01-04 04:19 UTC (permalink / raw) To: Jim C. Nasby <[email protected]>; +Cc: Tom Lane <[email protected]>; [email protected]; Tino Wildenhain <[email protected]>; Andre Truter <[email protected]>; pgsql-docs Jim C. Nasby wrote: > On Tue, Jan 03, 2006 at 04:20:38PM -0800, Joe Conway wrote: >>Well I like {prefix}/doc given that's how dblink is already set up ;-) >> > By {prefix} do you mean where PostgreSQL is being installed? If so, that > would be highly non-standard. I think what you'd want is > {prefix}/share/doc/postgresql/contrib/. Well, I assumed Tom was referring to placement in the source tree, i.e. {prefix} is contrib/dblink, etc. But this raises a good question in terms of where these files should be installed. The README.xxx files all go to {install-prefix}/doc/contrib. I experimented with changing the Makefile line: DOCS = README.dblink to be: DOCS = README.dblink doc/* Unfortunately the files from contrib/dblink/doc still wound up being installed to {install-prefix}/doc/contrib, which would become a naming collision hazard. Maybe they should go to {install-prefix}/doc/contrib/xxx (where xxx is the name of each contrib dir)? Joe ^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: Supplemental contrib docs @ 2006-01-04 05:03 Tom Lane <[email protected]> parent: Joe Conway <[email protected]> 0 siblings, 0 replies; 25+ messages in thread From: Tom Lane @ 2006-01-04 05:03 UTC (permalink / raw) To: Joe Conway <[email protected]>; +Cc: Jim C. Nasby <[email protected]>; [email protected]; Tino Wildenhain <[email protected]>; Andre Truter <[email protected]>; pgsql-docs Joe Conway <[email protected]> writes: > Well, I assumed Tom was referring to placement in the source tree, i.e. > {prefix} is contrib/dblink, etc. I'm concerned about both location in the source tree (dblink and tsearch2 are inconsistent) and location in the installation tree. The former seems easy to resolve: doc/ is the universal standard directory name for documentation, not docs/. I am not sure that we want to commit to creating a pile of subdirectories under the installation doc/ directory, though. If they were mostly full, fine, but a bunch of directories that are mostly empty would just be clutter. Maybe create subdirectories only for modules that have 'em in the source tree? regards, tom lane ^ permalink raw reply [nested|flat] 25+ messages in thread
end of thread, other threads:[~2006-01-04 05:03 UTC | newest] Thread overview: 25+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2005-12-17 12:53 DBlink documentation Andre Truter <[email protected]> 2005-12-17 13:20 ` Leonel Nunez <[email protected]> 2005-12-17 13:44 ` Andre Truter <[email protected]> 2005-12-17 14:04 ` Leonel Nunez <[email protected]> 2005-12-17 14:14 ` Andre Truter <[email protected]> 2005-12-17 14:21 ` Douglas McNaught <[email protected]> 2005-12-17 14:33 ` Russ Brown <[email protected]> 2005-12-17 14:37 ` Douglas McNaught <[email protected]> 2005-12-17 14:53 ` Greg Sabino Mullane <[email protected]> 2005-12-17 16:03 ` Andre Truter <[email protected]> 2005-12-18 04:35 ` Karl O. Pinc <[email protected]> 2005-12-17 14:53 ` Andre Truter <[email protected]> 2005-12-17 16:09 ` Tino Wildenhain <[email protected]> 2005-12-17 18:02 ` Andre Truter <[email protected]> 2005-12-17 18:31 ` Tom Lane <[email protected]> 2005-12-17 20:17 ` Joe Conway <[email protected]> 2005-12-17 20:47 ` Tom Lane <[email protected]> 2005-12-17 21:10 ` Bruce Momjian <[email protected]> 2005-12-19 21:55 ` Jim C. Nasby <[email protected]> 2006-01-03 23:52 ` Joe Conway <[email protected]> 2006-01-03 23:56 ` Tom Lane <[email protected]> 2006-01-04 00:20 ` Supplemental contrib docs (was: [GENERAL] DBlink documentation) Joe Conway <[email protected]> 2006-01-04 02:19 ` Re: Supplemental contrib docs (was: [GENERAL] DBlink documentation) Jim C. Nasby <[email protected]> 2006-01-04 04:19 ` Re: Supplemental contrib docs Joe Conway <[email protected]> 2006-01-04 05:03 ` Re: Supplemental contrib docs Tom Lane <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox