Re: src/tools/pginclude considered harmful (was Re: [PATCHES]

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Kris Jurka <books(at)ejurka(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: src/tools/pginclude considered harmful (was Re: [PATCHES]
Date: 2006-07-14 20:37:43
Message-ID: 44B80097.1080104@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>I agree with reverting. The tool looks pretty broken anyway, with
>>hardcoded paths and all sorts of stuff quite apart from logic problems.
>>
>>
>
>Well, it's only intended to work on Bruce's system, so until someone
>else takes over the position of chief gruntwork-doer I don't think the
>portability issues are much of a factor.
>

Shouldn't the README reflect that, then?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-07-14 20:38:56 Re: src/tools/pginclude considered harmful (was Re: [PATCHES]
Previous Message Zoltan Boszormenyi 2006-07-14 20:30:41 Re: Three weeks left until feature freeze

Browse pgsql-patches by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-07-14 20:38:56 Re: src/tools/pginclude considered harmful (was Re: [PATCHES]
Previous Message Tom Lane 2006-07-14 20:24:59 Re: src/tools/pginclude considered harmful (was Re: [PATCHES]