Re: ecpg and bison again

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ecpg and bison again
Date: 2002-06-19 13:06:31
Message-ID: 3591.1024491991@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Tue, Jun 18, 2002 at 04:41:57PM -0400, Tom Lane wrote:
>> Michael Meskes <meskes(at)postgresql(dot)org> writes:
> How about we add the preproc.c file generated by bison 1.49 to cvs?
> Could that create problems elsewhere?
>>
>> Yes. It's a bad idea to put derived files in CVS. For one thing,
>> CVS will not guarantee that their timestamps are right compared to
>> the master file.

> Actually I thought about changing the makefile as well, so preproc.c
> does not look like a derived file anymore.

That cure would be FAR worse than the disease. Leave it be.

The time for panic will be in August, if we are ready to make a beta
release and there's still no bison release. In the meantime I really
don't see why you can't keep updating your copy of preproc.y and
just not commit it...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2002-06-19 13:12:03 Re: ECPG won't compile anymore
Previous Message Tom Lane 2002-06-19 12:45:43 Re: Roadmap for a Win32 port