From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] Patch to fix plpython on OS X |
Date: | 2005-08-03 09:10:19 |
Message-ID: | 200508031110.20510.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Am Freitag, 29. Juli 2005 16:34 schrieb Tom Lane:
> Yeah. I desisted from deleting it after I noticed that there are
> provisions for re-generating it over in the doc/src/sgml Makefile.
> However, I'm now wondering why it's not handled exactly like INSTALL
> --- ie, don't keep it in CVS, but auto-generate it during tarball build.
> The current manual procedure definitely isn't keeping it up to date.
I don't see where the INSTALL file is generated either and put in place
either. I suppose this is somewhere in the release building scripts. It
should probably be done in the makefiles.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-08-03 12:23:33 | CVS repository for translations |
Previous Message | Peter Eisentraut | 2005-08-03 08:31:46 | Re: Information Schema DBMS VERSION wrong |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-08-03 09:22:11 | Re: Updated instrumentation patch |
Previous Message | Alon Goldshuv | 2005-08-02 15:03:44 | Re: [PERFORM] COPY FROM performance improvements |