Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Mike Aubury wrote:
>> Theres also another thing that needs to be decided, which is if the
>> generated
>> ecpg grammer should be developer generated (ie. Michael Meskes runs a script
>> and commits the output), or should be generated for each and every source
>> based installation. I personally would stongly favour the script being a
>> tool
>> for ecpg tool developers and not used as part of a normal installation.
> What happens when a non-Michael developer changes the original gram.y?
> Is he expected to run the script before committing too? That sounds
> brittle to me.
As long as the script is written in Perl and not exceedingly slow,
I see no reason it shouldn't be required to run as part of a build from
CVS. We already require Perl use elsewhere in the build if you're not
working from a tarball.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
