From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Configure problem, redux (was Re: TCL installation troubles) |
Date: | 1998-10-27 23:14:21 |
Message-ID: | 199810272314.SAA03613@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I certainly agree we should use configure for what it's designed to do,
> namely make intelligent configuration settings. I'm just saying that
> it is better style to record each configuration choice in only one place
> (or at least, as few places as possible) rather than make a bunch of
> copies in a bunch of not-easily-found files.
>
> This has advantages even if you don't consider hand adjustments to be
> important. Right now, if you want to find out what configure did on a
> given system, you need to look at twenty different files. (Some will
> give you no new information, but which ones?) Maintenance and support
> will be easier if there are only a couple of files that configure
> changes, and everything else just reads those files during build.
But your Makefiles become little 'sed' monsters, making it _more_
confusing for people to edit the Makefiles.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-10-27 23:18:38 | Re: [HACKERS] Sigh, build is broken again |
Previous Message | Thomas G. Lockhart | 1998-10-27 23:03:38 | Re: [HACKERS] configure and cpp detection |