Re: [pgsql-advocacy] Increased company involvement - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [pgsql-advocacy] Increased company involvement
Date
Msg-id 200505031246.19426.peter_e@gmx.net
Whole thread Raw
In response to Re: [pgsql-advocacy] Increased company involvement  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [pgsql-advocacy] Increased company involvement  (Stephen Frost <sfrost@snowman.net>)
Re: [pgsql-advocacy] Increased company involvement  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [pgsql-advocacy] Increased company involvement  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: [pgsql-advocacy] Increased company involvement  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
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.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: ARCHIVE TABLES (was: possible TODO: read-only
Next
From: "Magnus Hagander"
Date:
Subject: Re: BTW, if anyone wants to work on it...