Jyri
 I have made few more changes to the draft. You can catch the latest 
version from here
http://wikis.sun.com/download/attachments/10390064/php_more_features-update-2.txt

 In the updated ARC draft, the following changes have been made

- Incorporate some of your feedback
- Deliver pear / mysql and pgsql extensions as separate packages. This 
is to address the concerns from the Web Stack community.

pl. see inline for the rest


Jyri Virkki wrote:
> Sriram Natarajan wrote:
>   
>>> 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.
>>>       
>>   
>> please take a look at the updated draft and let me know if the 
>> explanation provided within addresses your concern.
>>     
>
> The 'pecl' CLI detail looks good, but I didn't see explanation about
> 'pear' yet, add something about it. I also see you added a new
> 'peardev' CLI, so also add a little info about its usage as well.
>
> All these CLIs will deliver man pages right? Also add a sentence
> saying so to the same section.
>
>   
- On further poking around, I see no reason to bundle 'peardev'. I have 
removed it.
- There will be no man page for 'pear' / 'pecl' command. Hence, it is 
not mentioned in the draft.
>>> So downloaded packages will be installed into this location?
>>>       
>>   
>> you could use /etc/php5/pear.conf to  specify where you want to download 
>> these extensions. 
>>     
>
> I know, I meant default location. It wouldn't hurt to mention the
> location can be changed in the config, if you want.
>
>   
Yes, I have added a few lines to mention this.
>> 2.6 Integration with Apache 
>>
>>        To provide closer integration of with Apache, provide php 
>>        specific configuration file(php.conf) under '/etc/apache/2.2/conf.d' 
>>        directory. This file will be delivered within SUNWapch2r-php5 package.
>>     
>
> Since it is tied to Apache 2.2 (delivering into /etc/apache/2.2/)
> shouldn't this be named SUNWapch22r-php5, to parallel the Apache
> package naming (SUNWapch22[dru])?
>
>   
Thanks for catching it.
I believe that these package names should be consistent with the Apache 
modules ARC draft that is being considered. What do you think ? Can we 
go with the current package name (SUNWapch22m-php5) or should we need to 
change it ?

thanks
sriram

Reply via email to