PHP ITP Status Update (was: [Maybe-ITP] PHP)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just a quick status update: I've now successfully hacked the buildsystem to produce the cgi-fcgi version of the binary a well as the cli version. I intend to try to tweak the build into producing a core DLL before posting any prospective packages -

Re: PHP ITP Status Update (was: [Maybe-ITP] PHP)

Max, I'd like you to take a look at Gentoo Linux PHP ebuild, http://www.gentoo.org/cgi-bin/viewcvs.cgi/dev-lang/php/ . It handles single-pass build of cli, cgi and apache module if fastbuild USE option is set and always worked fine to me.You can get great ideas how to run single pass cygwin php

Re: [Maybe-ITP] PHP

Max Bowsher schrieb: Reini Urban wrote: Well, postgresql is currently one big monolithic package. To make dependencies easier, I could provide the cygpg.dll client lib in a seperate libpg8 package, so that you could talk to a remote postgresql server at least. ok? This would certainly

Re: [Maybe-ITP] PHP

Max Bowsher wrote: I suggest to add FastCGI support (very useful with lighttpd package) and Umm. My current build doesn't include CGI support, let alone FastCGI. Oooops. Your're perfectly right. Me and a friend of mine tought about it for long in order to produce a multiple (both Apache and

Re: [Maybe-ITP] PHP

[my first answer was posted from my gmail account, so rejected] Max Bowsher schrieb: I don't have much of a liking for PHP myself, but seeing the large quantity of people who _do_ want it, and being the apache2 maintainer, I feel like I ought to at least make a bit of an effort to make it

Re: [Maybe-ITP] PHP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reini Urban wrote: Well, postgresql is currently one big monolithic package. To make dependencies easier, I could provide the cygpg.dll client lib in a seperate libpg8 package, so that you could talk to a remote postgresql server at least. ok?

Re: [Maybe-ITP] PHP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Max Bowsher wrote: Given the above caveats, do you think I should proceed with the ITP process, or not? Lapo Luchini wrote: I had tought to do this ITP too, but as I'm already enough behind schedule with existing packages I always delayed this

[Maybe-ITP] PHP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't have much of a liking for PHP myself, but seeing the large quantity of people who _do_ want it, and being the apache2 maintainer, I feel like I ought to at least make a bit of an effort to make it available. So: I have prospective PHP

Re: [Maybe-ITP] PHP

Max Bowsher maxb1-B2Gdhv0Jo/[EMAIL PROTECTED] writes: I don't have much of a liking for PHP myself, but seeing the large quantity of people who _do_ want it, and being the apache2 maintainer, I feel like I ought to at least make a bit of an effort to make it available. So: I have prospective

Re: [Maybe-ITP] PHP

On Thu, April 27, 2006 5:57 pm, Max Bowsher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't have much of a liking for PHP myself, but seeing the large quantity of people who _do_ want it, and being the apache2 maintainer, I feel like I ought to at least make a bit of an effort

Re: [Maybe-ITP] PHP

Max Bowsher wrote: Given the above caveats, do you think I should proceed with the ITP process, or not? I had tought to do this ITP too, but as I'm already enough behind schedule with existing packages I always delayed this to later... I would obviously appreciate it. I suggest to add FastCGI

Re: [Maybe-ITP] PHP

Max Bowsher wrote: (1) I'm linking to postgresql. PHP without any SQL database interface would be a bit crippled - on the other hand, this requires *everyone* installing PHP to install PostgreSQL. It *ought* to be able to modularize the dependency into a sub-package, but persuading the