Re: build farm failures - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: build farm failures
Date
Msg-id 20070816200457.GA27775@alvh.no-ip.org
Whole thread Raw
In response to Re: build farm failures  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: build farm failures  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan wrote:
>
>
> Michael Meskes wrote:
>> The backend has:
>>
>> $(srcdir)/gram.c: $(srcdir)/parse.h ;
>>
>> $(srcdir)/parse.h: gram.y
>>
>> So except for the different naming it's the same. However, we haven't
>> had that problem with the backend so far, or did we?
>>
>> What do I fail to see?
>
> We have had problems in the past. If the user builds at a point in time 
> after the .y file is checked in then the generated file is newer and if 
> it's not removed will never be regenerated, even if they do a subsequent 
> cvs update.

How do you create the copy of the repo to build?  One idea would be to
explicitely skip files that appear on .cvsignore (and maybe croak about
them).

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Another idea for index-only scans
Next
From: Decibel!
Date:
Subject: Re: Another idea for index-only scans