From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
Subject: | RPM source files should be in CVS (was Re: psql -l) |
Date: | 2001-07-19 02:42:00 |
Message-ID: | 21888.995510520@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> On Wednesday 18 July 2001 18:03, Bruce Momjian wrote:
>> The strange part is that we are running around trying to figure out if
>> it is a bug and no one knows that Debian has modified it.
> While I understand Oliver's reasons for having the Debian stuff on the
> debian server, I believe it would be appropriate to have the patchfile
> and the various Debian README's available on the main postgresql site.
ISTM that it'd be a good thing if current versions of all the add-on
source files for both Debian and RedHat RPMs were part of our CVS tree
(perhaps in /contrib, perhaps somewhere else, but anyway in the tree).
Had I been able to find that "No database specified" string by grepping
the sources, I'd have been much less mystified. Likewise for the "peer"
question a week or two back, and the questions we sometimes get about
the behavior of startup scripts that aren't even part of our tarball.
This sort of thing is going to keep coming up, so we might as well admit
that we need to know what is in the RPMs.
Oliver, Lamar, what say you?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2001-07-19 03:55:15 | Re: RPM source files should be in CVS (was Re: psql -l) |
Previous Message | Dr. Evil | 2001-07-19 02:05:07 | Re: pl-sql |
From | Date | Subject | |
---|---|---|---|
Next Message | Horst Herb | 2001-07-19 03:03:28 | Re: OID wraparound (was Re: pg_depend) |
Previous Message | Hiroshi Inoue | 2001-07-19 02:19:04 | Re: pg_depend |