From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Lessons from commit fest |
Date: | 2008-04-17 17:53:46 |
Message-ID: | 23273.1208454826@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I have been thinking of pursuing your suggestion of having it as a
> buildfarm option. We could provide a SOAP interface to collect the
> typedefs and then consolidate them and put them in CVS. We could even do
> it per release. That would include Windows, although only MinGW, not
> MSVC, which doesn't have objdump.
That would certainly be better than the current approach, since
presumably it would cover not only Windows but the other
conditionally-compiled stuff that Bruce chooses not to compile on
his own machine.
Note though that the existing find_typedef script only works on (some
variants of) Linux and BSD. Porting it to a wider set of platforms
might be pretty painful.
I still wish we could build the list directly from the source code,
but I have no suggestions for tools that would do it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-04-17 18:09:04 | Re: Plan targetlists in EXPLAIN output |
Previous Message | Alvaro Herrera | 2008-04-17 17:46:31 | Re: Lessons from commit fest |