| >| Can you also point out as to why these modules warrant a specific
| >| 'SUNWapch2m' package and why they are not being delivered with the rest
| >| of the Apache modules
| >It is so that they are easier to manage. (The modules mod_jk and
| >mod_fcgid are going to be part of that package, and they are not part of
| >the apache httpd source. *ldap* modules are part of the SUNWapch2u)
| >
| If 'ldap' modules are part of Apache HTTPd source, then we should be
| tracking this 'ldap' module as part of Apache ARC case , isn't it ?
Perhaps, They were made part of the modules ARC case so as to not to
delay Apache2 ARC further. (Arvind/Jyri could you please comment?)
| >When mod_python/ruby/etc comes in they will also be part of the modules
| >package.
| >
| Hmm.. does this mean - php module for apache httpd should also be part
| of this package ? If not, then why the inconsistency between different
| components in the WebStack. On the same note, does a ruby module require
The major function of php is to supply mod_php. but this is not the case
with either ruby or python. That said, I would like to see a discussion
on where the mod_ruby and mod_python belongs in this group when they
come up for their inclusion.
| Ruby runtime or other Ruby configuration file (SUNWrubyr ? ) . If yes,
| then the package of this module will need to appropriately capture its
| dependency as well, isn't it ?
Yes. the ARC cases for those apache modules will have this dependency
nailed down.
rahul
--
1. e4 _
