Re: Feasibility of splitting out web components of lang/php5
On Thu, 05 Jan 2012, 20:20 -0800, Doug Barton wrote: > What would make my life a whole lot simpler is if lang/php5 were the > command line version, and the cgi and apache modules were separate > ports. Is this feasible? Don't the port's knobs work for you? If I set the CGI knob off, I get what I think you want. OPTIONS=CLI "Build CLI version" on \ CGI "Build CGI version" on \ FPM "Build FPM version (experimental)" off \ APACHE "Build Apache module" off \ AP2FILTER " Use Apache 2.x filter interface (experimental)" off \ DEBUG "Enable debug" off \ SUHOSIN "Enable Suhosin protection system" on \ MULTIBYTE "Enable zend multibyte support" off \ IPV6 "Enable ipv6 support" on \ MAILHEAD "Enable mail header patch" off \ LINKTHR "Link thread lib (for threaded extensions)" off -- John Marshall pgp0fJW2HTzZO.pgp Description: PGP signature
Re: Feasibility of splitting out web components of lang/php5
On 01/05/2012 21:45, John Marshall wrote: > On Thu, 05 Jan 2012, 20:20 -0800, Doug Barton wrote: >> What would make my life a whole lot simpler is if lang/php5 were the >> command line version, and the cgi and apache modules were separate >> ports. Is this feasible? > > Don't the port's knobs work for you? Um, I understand how options work, but thank you for your response. If I wasn't clear about what I'm looking for I apologize for the confusion. I want to have the command line (only) version of php, AND the web stuff, on the same package building system. That way I can support all my end systems with the same sets of packages. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Feasibility of splitting out web components of lang/php5
On Fri, 6 Jan 2012 16:45:53 +1100 John Marshall wrote: > On Thu, 05 Jan 2012, 20:20 -0800, Doug Barton wrote: > > What would make my life a whole lot simpler is if lang/php5 were the > > command line version, and the cgi and apache modules were separate > > ports. Is this feasible? > > Don't the port's knobs work for you? If I set the CGI knob off, I get > what I think you want. > They are works for all (I think). But Doug ask about _separate_ ports 2 Doug: IIRC long time ago was www/mod_php[45], but It was removed by ade@. It might be worth restore them? (personally I'm interested in php_fpm slave port) > OPTIONS= CLI "Build CLI version" on \ > CGI "Build CGI version" on \ > FPM "Build FPM version (experimental)" off \ > APACHE "Build Apache module" off \ > AP2FILTER " Use Apache 2.x filter interface > (experimental)" off \ DEBUG "Enable debug" off \ > SUHOSIN "Enable Suhosin protection system" on \ > MULTIBYTE "Enable zend multibyte support" off \ > IPV6 "Enable ipv6 support" on \ > MAILHEAD "Enable mail header patch" off \ > LINKTHR "Link thread lib (for threaded extensions)" > off > -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Feasibility of splitting out web components of lang/php5
06.01.2012 06:20, Doug Barton wrote: I do package build systems that support a variety of types of end systems. (Nearly) all of them use php in some form or another, but a substantial portion of them don't have web servers, and therefore don't need the cgi, apache module, or the apache dependency that comes with them. What would make my life a whole lot simpler is if lang/php5 were the command line version, and the cgi and apache modules were separate ports. Is this feasible? Long long ago when I was building php on linux by hand I noticed that cgi/apache/standalone binaries differ only in small subset of linker objects i.e. splitting this into many ports will made us for sure recompile whole php for each of them. So: * this is good from the installation perspective, when user can select which packages to install and have the components he really needs; * this is boring from the update perspective for those who build php by hand. I'd say that both options would be good to have. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Feasibility of splitting out web components of lang/php5
Doug Barton ha scritto: What would make my life a whole lot simpler is if lang/php5 were the command line version, and the cgi and apache modules were separate ports. Is this feasible? Short answer: no. Long answer: nothing is impossible ;-) Extensions are compiled based on settings of the core php. If you split core php in different ports, you end up with possibly many different settings (e.g, standard CLI, debug CGI, threaded mod_php) and so it's impossible to compile extensions that work for all SAPIs. In an ideal world, the core php should compile only a shared library, and the various SAPIs should link it. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
