| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgsql-advocacy] Increased company involvement |
| Date: | 2005-05-03 14:43:03 |
| Message-ID: | 8772.1115131383@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Montag, 2. Mai 2005 20:14 schrieb Bruce Momjian:
>> I posted this compromise and no one replied so I thought everyone was OK
>> with it. It gets it into CVS, but has a separate compile stage to deal
>> with the recursive dependency problem.
> How will a "separate compile stage" work for actually building, say, RPM or
> Debian packages? The only way I can see is wrapping up the PostgreSQL
> distribution tarball a second time as a "plphp" source package and build from
> there, which seems quite weird.
I think the idea is that plphp would be in our CVS, but would not be
shipped as part of the main tarball, rather as its own separate tarball.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-05-03 15:07:42 | Re: [pgsql-advocacy] Increased company involvement |
| Previous Message | Stephen Frost | 2005-05-03 13:38:19 | Re: [pgsql-advocacy] Increased company involvement |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Held | 2005-05-03 14:59:47 | Re: Feature freeze date for 8.1 |
| Previous Message | Tom Lane | 2005-05-03 14:37:08 | Re: bitmap scan and explain analyze |