Spoke too soon (was RE: cvs committers digest)

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Spoke too soon (was RE: cvs committers digest)
Date: 2000-02-05 22:12:16
Message-ID: 389CA040.D5CBC94F@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Lamar Owen wrote, in a misguided moment: (:-/)
> I also track the current CVS -- but for a totally different reason, as I
> want to be able to release RPMs of the beta release the same day as the
> beta release -- thus, I am doing trial builds of RPM's against the CVS.
> However, this current issue doesn't impact me in the slightest -- which
> is why I have not and will not say anything about it.

I am now saying something about it. While I have been doing trial
builds of the current sources, I have not been building all the clients
up until today, for speed in building. And guess what -- the lack of
pqbool breaks the perl5 client. Badly. Won't-even-compile-badly.

Is this breakage going to be fixed by the 15th? If not, what can I do
to workaround it until it is fixed properly (either by putting pqbool
back in libpq-fe.h, or by fixing Pg.xs to not need pqbool).

I _would_ like to have RPM's ready of the beta on the release day....

TIA

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-02-05 22:26:06 Re: [HACKERS] Spoke too soon (was RE: cvs committers digest)
Previous Message Bruce Momjian 2000-02-05 22:01:59 Re: [HACKERS] Proposal for new SET variables for optimizer costs