> I'm curious if php is commonly invoked manually from > the shell command > line? (Since that's the main reason to have something > in the default PATH.)
If PHP has been so compiled, the compiler and the linker will generate a php binary for use in the CLI and for running PHP scripts. Personally, I believe this is great feature, becayse it not only adds one more powerful, flexible language for writing scripts, but also for building complex and powerful applications, to Solaris. My hope is that the CLI version of PHP becomes the norm. Right now Solaris is on the good track to be one of the first, if not the first, early adopters to add CLI PHP to his arsenal. This is cutting edge stuff, and it creates a great incentive for developers to use Solaris and develop on it. > When invoked programmatically you might not want to > call /usr/bin/php > anyway because you can't predict which version it is > so the behavior > can change in a Volatile way. Whereas if you call > /usr/php5/5.2.4/bin/php > you know its behavior will remain constant. This leaves doubt in my mind. Has PHP really changed in such drastic ways from 4.x to 5.x that it actually warrants the /usr/php/<revision>/ directory tree? I find that really hard to believe. What particularly concerns me is the following: PSARC 2007/168 proposes, among other things, a file system structures for PHP5. However, nowhere in that proposal do I see any sparcv9/ directories, which implies that only 32-bit version of PHP will be delivered. I use Oracle as a backend for my PHP development and applications. But, Oracle delivers only 64-bit binaries and libraries on Solaris SPARC. So in order to enable Oracle functionality in PHP, one deliver a 64-bit version of PHP. Not only that, but any additional functionality desired in PHP, like PostgreSQL, Net-SNMP, Cyrus-SASL, OpenLDAP, OpenSSL, and so on, must also be compiled 64-bit. And I believe, that I am not at all a lone consumer of the Oracle-PHP tandem. After all, PHP is officially supported by the Oracle database. So my question is this: with the above in mind, does PSARC 2007/168 foresee delivering both 64- and 32-bit versions of PHP, or just the 32-bit version? If just 32-bit version is delivered, then I am forced to continue maintaining my own webstack. (I deliver both 32- and 64-bit binaries and libraries of all the features I used in PHP, including PHP himself.) This message posted from opensolaris.org
