> Yes, the CLI is there, /usr/php5/5.2.4/bin/php > > The earlier part of this thread was just about adding > a soft link > /usr/bin/php -> /usr/php5/5.2.4/bin/php
For my part, I would very much like to see php be available as /usr/bin/php. What is the final consensus on this matter? > Well, the change doesn't necessarily have to be so > drastic, if there > is a break in compatibility then it is worth having > some versioning. Makes sense. > But this is an area that should be explored further. > IMO the original > case was overly conservative with the > /usr/php5/5.2.4/ versioning. I > believe this is going to have to be revised because > delivering a whole > new set of packages for every bug fix is too > cumbersome. > > The question will be what is the correct level of > versioning - i.e. at > what dot release level can we expect incompatibility. > Apache and Ruby > for example went with "X.Y", expecting all X.Y.* will > be compatible. In my experience, for PHP, making a distinction between "php4" and "php5" is enough. With this in mind, I propose that the packages be renamed before Nevada is solidified into the next release of Solaris. Current naming is "SUNWphp520", whereas in my experience "SUNWphp5r" and "SUNWphp5u" would have been just fine (and elegant). > Correct, 2007/168 delivered 32bit PHP into build 76. > Support for 64bit > PHP hasn't been done yet. It's something that'd be > nice to look into. > > (As always, if you|anyone wants to share experience, > needs or best of > all, build system patches, all comments are welcome!) Please be advised that I am currently working on building a complete 32- and 64-bit PHP stack, which includes, but is not limited to (all components delivered as both 32- and 64-bit) - OpenSSL - OpenLDAP - CyrusSASL - PostgreSQL - Net-SNMP - libz - bzip2 - Oracle instant client and finally PHP 5.2.x (whichever the latest revision will be). I am currently "stuck" packaging PostgreSQL, since the 64-bit version came too late for me, which turned out to be a package metacluster with several packages. Once I get PostgreSQL out of the way, I'll move on to the Oracle instant client packaging, and finally to compiling and linking PHP against all of these components, then packaging of the same. I have been able to produce a prototype version of PHP 5.2.3 with all of these components on the i86pc platform, but it was 32-bit, since Oracle still supports 32-bit on Solaris i86pc platform. The binary is dynamically linked, however the size is still nothing to sneeze at, at almost 15MB. What I'm wondering is, is there any way to combine our efforts, so that there is no duplication of work? For my part I can offer extensive experience getting open source software to compile & link on Solaris with Sun Studio compilers, and I also have extensive experience producing Solaris System V packages. This message posted from opensolaris.org
