On Tue, 3 May 2005, Tom Lane wrote:

> Peter Eisentraut <peter_e@gmx.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.

That is what I'm hoping for ... if it can be shipped as a seperate
tarball, my arguments *against* including it become moot, since packagers
(and ports) can have a nice small, quick to download package instead of
having to re-download a >11MB file each time ...

I don't mind if its *also* ship'd in the main distribution as well, I just
want that 'quick to download since I already have the libraries/headers
installed' package ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq