Sriram Natarajan wrote:
>
>   Please find an initial DRAFT on the proposed  'PHP5  Feature 
> Enhancements'  that we are planning to integrate within OpenSolaris.
> http://wikis.sun.com/download/attachments/10390064/php_more_features.txt

>         2.2 Memcache[4] external extension will be bundled 
[...]
>         PHP Memcache module is being bundled to integrate with Memcached 
>       server that is being delivered within OpenSolaris.

AFAIK it hasn't integrated quite yet so add a clause that "this module
will be integrated only after memcached has integrated."


>         2.3 PEAR/PECL support will be provided
[...]
>         /usr/php5/5.2.4/bin/pear
>         /usr/php5/5.2.4/bin/pecl

The text in this section doesn't make a very clear distinction between
the two CLIs being delivered, for which purpose is each one used. I
suggest adding a few sentences to that effect.

>         PEAR comes built-in with an internal repository. These files
>         will be kept under /var/php5/5.2.4/pear directory. These files
>         are listed under the Appendix' section.

So downloaded packages will be installed into this location?

The appendix shows a very large list of pre-installed code. Why are
these needed? Also, as discussed during ruby gems case, why are they
in /var (the answer might be same as for gems, but discuss it in the text).



> 4. References
> 
>         [5] http://www.opensolaris.org/os/community/arc/caselog/2007/608/
>       [13] http://sac.sfbay/LSARC/2007/608/

13 is duplicate of 5, keep [5] as it is the opensolaris link


> ============================================================================
> Appendix A: Output of 'find /var/php5/5.2.4/pear/'
> 
> NAME                                  STABILITY                       
>       /var/php5                                               Uncommited

The appendix is just a listing of files, you don't need to declare a
stability for every *.php file individually. Remove the stability
column here, it should be covered in exported interface table already.


-- 
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems

Reply via email to