>> This is a general purpose portable OSS library like glib or others. Should
>> it really go under "web"? (obviously a web server depends on it)
>
> It's the only thing under web/library, and the meaning of "apache" leaves room
> for doubt (httpd or asf?). +1 to drop the web.
This should be addressed in the next build.
>> b. SUNWspawn-fcgi web/fastcgi/spawn-fcgi
>>
>> Shouldn't this go under web/server?
>
> Disagree, unless the whole of fastcgi goes there.
Any suggestions on where to put this then?
>> d. SUNWapch22m-fcgid web/server/apache-22/plugin/plugin-fastcgi
>>
>> Why does "plugin" have to be repeated?
>>
>> mod_fcgid is a particular implementation of FastCGI for httpd; mod_fastcgi
>> is another. Thus, the package name should use the "fcgid" string.
>
>> Generally the exact name of the plug-in (after s/mod_// and s/_/-/) should
>> appear in the package name.
>
> +1. Ditto other packages in the same collection: you didn't mention such
> atrocities as plugin-php52
Well, the module is "mod_pgp5.2" so the package name seems to follow
the scheme.
>> e. SUNWapch22m-jk web/server/apache-22/plugin/plugin-tomcat
>>
>> another case where I think the specific mod name ("jk") should be used;
>> Tomcat Connectors is a big project with multiple plug-ins (also, mod_jk can
>> be used with GF)
>
> +1 to jk as far as it goes. Having this as a separate module while AJP is
> bundled
> jars a bit, but that's down to upstream.
Yes, we'll address this in the next build.
>> f. SUNWapch22m-proxy-html web/server/apache-22/plugin/plugin-html-plugin
>>
>> What the heck :) I hope that's a typo on the wiki.
>>
>> (image-update+reboot finished; pkg search shows
>> "pkg:/web/server/apache-22/plugin/plugin-html-plugin at 3.1.1-0.133")
>
> Hehe. Looks like a typo, but not so clear where it originates!
This as well.
