If I am not mistaken, SUNWCapch22m is a package cluster that makes sense
only while filing package rti. in real world - either in nevada or in
indiana (opensolaris 2009.xx), SUNWCapch22m cluster is not integrated
thanks
sriram
Jeff Trawick wrote:
> Brian Overstreet wrote:
>> 4. Packaging and Delivery
>>
>> The module mod_wsgi will be delivered under the cluster
>> SUNWCapch22m under the name SUNWapch22m-wsgi in keeping with the
>> naming of other external Apache modules.
>>
> BTW, how would I query SUNWCapch22m to see what is there now?
>
> Example for "amp" cluster:
>
> $ pkg contents -r -m amp
> set name=fmri value=pkg:/amp at 0.5.11,5.11-0.101:20081119T235643Z
> set name=description value="Cluster containing an AMP (Apache, MySQL,
> PHP) deployment kit"
> set name=info.classification value="org.opensolaris.category.2008:Web
> Services/Application and Web Servers"
> set name=authority value=opensolaris.org
> depend fmri=SUNWapch22m-security at 2.1.5-0.101 type=require
> depend fmri=SUNWmysql5 at 5.0.67-0.101 type=require
> depend fmri=SUNWapch22m-dtrace at 0.3.1-0.101 type=require
> depend fmri=SUNWphp52 at 5.2.6-0.101 type=require
> depend fmri=SUNWapch22 at 2.2.9-0.101 type=require
> depend fmri=SUNWphp52-mysql at 5.2.6-0.101 type=require
> depend fmri=SUNWapch22m-fcgid at 2.2-0.101 type=require
> depend fmri=SUNWapch22m-php52 at 5.2.6-0.101 type=require
>
> pkg fails to find SUNWCapch22m or SUNWapch22m.
>
>> 5.2. Imported Interfaces
>>
>> These Apache modules imports interfaces from
>>
>> NAME STABILITY NOTES
>> ------------------------------------------------------------
>> Apache2 Uncommitted PSARC/2007/586/
>> SUNWPython External PSARC/2009/043
>>
>
> What are the ramifications for the several levels of Python planned
> for 2009.06? Does mod_wsgi work with a specific Python level or all of
> them? Should we specifically call out some/all of (SUNWPython25,
> SUNWPython26, SUNWPython30)?
>
>> 5.3. Exported Interfaces
>>
>> NAME STABILITY
>> ---------------------------------------------------------------
>> /usr/apache2/2.2/libexec/mod_wsgi.so Volatile
>> /usr/apache2/2.2/libexec/${ISAINFO}/mod_wsgi.so Volatile
>> /usr/apache2/2.2/libexec/mod_sed.so Volatile
>> /usr/apache2/2.2/libexec/${ISAINFO}/mod_sed.so Volatile
>>
>> /etc/apache2/2.2/conf.d/wsgi.conf Volatile
>> /etc/apache2/2.2/conf.d/sed.conf Volatile
>>
>
> I'm guessing that mod_sed for example isn't going to edit the
> responses from my web server until I go edit some config files. I
> don't have any guesses about the out of the box suitability of wsgi.conf.
>
> General consideration with conf files for add-on Apache modules:
>
> If the user must make a modification to the config snippet (e.g.,
> wsgi.conf or sed.conf) in order to have the module perform any useful
> work, shouldn't we put the config snippet in the samples-conf.d
> directory instead of the conf.d directory?
>
> Note that dtrace and php are automatically loaded/configured via
> conf.d and can actually serve a useful purpose out of the box without
> further configuration work. (I guess jk.conf serves some servlet
> examples installed with Tomcat.)
>
> _______________________________________________
>
>
> webstack-discuss mailing list
> webstack-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
