On Sun, Jan 3, 2010 at 05:13, Andrew Dunstan wrote:
>
>
> Peter Eisentraut wrote:
>>
>> On fre, 2010-01-01 at 16:32 +0100, Magnus Hagander wrote:
>>
>>>
>>> I therefor propose that we rename this file to "config.pl.default",
>>> and change the scripts to first load config.pl.default, and then load
Andrew Dunstan wrote:
> I don't think the "parens on trailing conditions" issue is anything
> other than just a matter of taste.
Agreed
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-hackers mailin
Peter Eisentraut wrote:
On fre, 2010-01-01 at 16:32 +0100, Magnus Hagander wrote:
I therefor propose that we rename this file to "config.pl.default",
and change the scripts to first load config.pl.default, and then load
config.pl if it exists.
I'd keep the naming so that the extensio
On fre, 2010-01-01 at 16:32 +0100, Magnus Hagander wrote:
> I therefor propose that we rename this file to "config.pl.default",
> and change the scripts to first load config.pl.default, and then load
> config.pl if it exists.
I'd keep the naming so that the extension .pl is preserved. Helps
edito
On Sat, Jan 2, 2010 at 02:20, Alvaro Herrera wrote:
> Magnus Hagander wrote:
>
>> I therefor propose that we rename this file to "config.pl.default",
>> and change the scripts to first load config.pl.default, and then load
>> config.pl if it exists. config.pl then lives completely outside the
>> s
Magnus Hagander wrote:
> I therefor propose that we rename this file to "config.pl.default",
> and change the scripts to first load config.pl.default, and then load
> config.pl if it exists. config.pl then lives completely outside the
> source tree (should be in .cvsignore) and won't show up in an
I'd like to apply the attached patch to the msvc build environment,
which changes how config.pl is handled. (For the unenlightened, this
is the replacement stuff we have for autoconf)
Today, there is one config.pl. We ship it with a couple of defaults
(which points to a very old installation of mi
