Hi all, upon request of Tilman ("I need a FCGI PHP") and Jose ("Why depends mod_php on mysql") I took a closer look at PHP, to get an idea how we can optimize the current situation. My proposed solution is based on four ports: - php: the PHP CLI interpreter plus some extension modules and support stuff like include-files - php-fcgi: CGI/FastCGI version of the interpreter with start script - php-apache: DSO module for apache - php-mysql: MySQL module as an example how to build extensions which are depending on external libraries. Some remarks: - Configuration files are now in /etc/php and /etc/php/conf.d. The later is scanned for *.ini files, see php-mysql for an example. - The modules build with php depends on core ports only, not checked for completeness. - php-fcgi and php-apache do not depend on php, so we have very slim ports if only the default extensions are needed. Both work, of course, together with php-mysql or other extensions like that. Please comment and test the attached ports. Thanks Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Juergen Daubert wrote:
Hi all,
upon request of Tilman ("I need a FCGI PHP") and Jose ("Why depends mod_php on mysql") I took a closer look at PHP, to get an idea how we can optimize the current situation.
Hi Jue, I supposed you are talking about the php5 branch. :)
My proposed solution is based on four ports:
- php: the PHP CLI interpreter plus some extension modules and support stuff like include-files
Nice, great job, I like the idea of discuss this kind of big ports, that can be ported in many different ways, with or without some dependencies. Of course I like the CLI.
- php-fcgi: CGI/FastCGI version of the interpreter with start script - php-apache: DSO module for apache
I think that php is an extension of apache, an not the reverse In the fooprint I can see that appears the apache library path: $ grep libphp5.so php-apache/.footprint -rwxr-xr-x root/root usr/lib/apache/libphp5.so I would keep the original mod_php instead of php-apache, sounds more reasonable (imho) if we take as reference some other apache base ports like mod_ruby, mod_perl, mod_python
- php-mysql: MySQL module as an example how to build extensions which are depending on external libraries.
sounds nice for contributing with more php based ports in future: php-bz2, php-curl, php-mcrypt, php-odbc, php-sqlite, php-xmlrpc, php-xsl, php-mhash, php-ldap, etc etc
Some remarks: - Configuration files are now in /etc/php and /etc/php/conf.d. The later is scanned for *.ini files, see php-mysql for an example. - The modules build with php depends on core ports only, not checked for completeness.
That's right.
- php-fcgi and php-apache do not depend on php, so we have very slim ports if only the default extensions are needed. Both work, of course, together with php-mysql or other extensions like that.
I'm studing some other systems like openbsd to get more ideas for comments. I think this one (obsd) has a great implementation of php / apache / mysql / fcgi / ... (I mean phpxs command too) I attached a file as an example for installing php and some more extensions for everyone who want to take a look. Many thanks, and regards Jose V Beneyto
Jose V Beneyto wrote:
Juergen Daubert wrote:
Hi all,
upon request of Tilman ("I need a FCGI PHP") and Jose ("Why depends mod_php on mysql") I took a closer look at PHP, to get an idea how we can optimize the current situation.
Hi Jue,
I supposed you are talking about the php5 branch. :)
My proposed solution is based on four ports:
- php: the PHP CLI interpreter plus some extension modules and support stuff like include-files
Nice, great job, I like the idea of discuss this kind of big ports, that can be ported in many different ways, with or without some dependencies. Of course I like the CLI.
- php-fcgi: CGI/FastCGI version of the interpreter with start script - php-apache: DSO module for apache
I think that php is an extension of apache, an not the reverse In the fooprint I can see that appears the apache library path:
$ grep libphp5.so php-apache/.footprint -rwxr-xr-x root/root usr/lib/apache/libphp5.so
- php-mysql: MySQL module as an example how to build extensions which are depending on external libraries. sounds nice for contributing with more php based ports in future:
I would keep the original mod_php instead of php-apache, sounds more reasonable (imho) if we take as reference some other apache base ports like mod_ruby, mod_perl, mod_python php-bz2, php-curl, php-mcrypt, php-odbc, php-sqlite, php-xmlrpc, php-xsl, php-mhash, php-ldap, etc etc sorry, bz2 and curl are included as extensions in the php base port
Some remarks: - Configuration files are now in /etc/php and /etc/php/conf.d. The later is scanned for *.ini files, see php-mysql for an example. - The modules build with php depends on core ports only, not checked for completeness.
That's right.
- php-fcgi and php-apache do not depend on php, so we have very slim ports if only the default extensions are needed. Both work, of course, together with php-mysql or other extensions like that.
I'm studing some other systems like openbsd to get more ideas for comments. I think this one (obsd) has a great implementation of php / apache / mysql / fcgi / ... (I mean phpxs command too) I attached a file as an example for installing php and some more extensions for everyone who want to take a look.
Regards, Jose V Beneyto
On Sat, May 03, 2008 at 01:38:02AM +0200, Jose V Beneyto wrote: [...]
I would keep the original mod_php instead of php-apache, sounds more reasonable (imho) if we take as reference some other apache base ports like mod_ruby, mod_perl, mod_python
Yes, that's right. I was too overeager putting everything into that php-* scheme, will keep mod_php. Thanks Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Hello, Jose. On Sat, 03 May 2008 01:38:02 +0200 Jose V Beneyto <sepen@users.sourceforge.net> wrote:
[...] I'm studing some other systems like openbsd to get more ideas for comments. I think this one (obsd) has a great implementation of php / apache / mysql / fcgi / ... (I mean phpxs command too) I attached a file as an example for installing php and some more extensions for everyone who want to take a look.
After playing a bit with this new php ports it still looks very KISS and quite extensible. But what about PEAR/PECL packages? opt/pear is somewhat outdated, new version has new deps and a quick version bump is not a sane way due to few '.reg' files that are not a part of PEAR tarball. Does anyone have an idea how to safely package PEAR/PECL extensions (maybe with essential meta information) in Pkgfile? -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta
Juergen Daubert [2008-05-02 23:55]:
Hi all,
upon request of Tilman ("I need a FCGI PHP") and Jose ("Why depends mod_php on mysql") I took a closer look at PHP, to get an idea how we can optimize the current situation.
My proposed solution is based on four ports: [snip]
Sounds good to me :) -- I didn't test them yet though. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
participants (4)
-
Jose V Beneyto -
Juergen Daubert -
Mikhail Kolesnik -
Tilman Sauerbeck