Re: Modest proposal: run check_keywords.pl on every build

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
Subject: Re: Modest proposal: run check_keywords.pl on every build
Date: 2012-09-27 02:00:52
Message-ID: 5063B354.7030604@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 09/26/2012 09:16 PM, Tom Lane wrote:
> I've had it with mopping up after oversights like this one:
> http://archives.postgresql.org/pgsql-hackers/2012-09/msg01057.php
>
> We made a script (src/tools/check_keywords.pl) to check for this type of
> error years ago, and even added it to the top-level "maintainer-check"
> target awhile back, but nonetheless people continue to screw it up on
> a regular basis (twice already this year alone). I think we should move
> the script into src/backend/parser and run it as part of the make gram.c
> target. (Doing it that way will not cause perl to become required for
> building from tarballs, since gram.c is supplied prebuilt in tarballs.
> And we already require perl for builds from raw git pulls.)
>
> Any objections?
>
>

works for me.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-09-27 02:06:50 Re: pg_upgrade does not completely honor --new-port
Previous Message md@rpzdesign.com 2012-09-27 01:17:24 Re: Switching timeline over streaming replication