Bruce Momjian <pgman@candle.pha.pa.us> writes:
My idea is that the second stage would just have them go to src/pl/plphp and type 'gmake install'.
Absolutely not. It has to work as an independent package, not as something that expects to build inside an already-configured Postgres source tree. That means its own configure etc.
Wait I am confused. Right now plPHP is setup to be a part of the source tree. It uses ./configure --with-php etc...
So where are we going?
Sincerely,
Joshua D. Drake
Basically, we can keep the files in our CVS for ease of maintenance, but that is not going to show up at all in terms of what is shipped in the two tarballs --- they will be independent products.
regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
-- Your PostgreSQL solutions provider, Command Prompt, Inc. 24x7 support - 1.800.492.2240, programming, and consulting Home of PostgreSQL Replicator, plPHP, plPerlNG and pgPHPToolkit http://www.commandprompt.com / http://www.postgresql.org
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
