Nick Kew wrote:
> On 20 Feb 2010, at 13:03, Jeff Trawick wrote:
>
>
>> http://hub.opensolaris.org/bin/view/Project+indiana/Renamed+Packages+in+Build+133
>>
>> I'll try to spend a little time to propose some changes; if anyone else is
>> going to bother to look at the Web Stack-related packages then we can
>> discuss here.
>>
>> A few questions/concerns from looking at the table for a few minutes:
>>
>> a. SUNWapr13 web/library/apache/apr-13
>> 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.
>
Potentially the FastCGI programming library could go under /web/library
(it is currently /library/fcgi).
>
>> b. SUNWspawn-fcgi web/fastcgi/spawn-fcgi
>>
>> Shouldn't this go under web/server?
>>
>
> Disagree, unless the whole of fastcgi goes there.
>
Shrug. The whole of fastcgi right now seems to be
mod_fcgid
FastCGI programming library
spawn-fcgi
I guess web/fastcgi for the latter two works for me. A "fastcgi"
category isn't going be so helpful long-term though since Perl language
bindings would be expected to be named like other Perl modules, and the
same for Python, Ruby, etc. (Just as httpd users would expect to be able
to find extra modules under a specific hierarchy.
>
>> c. SUNWphp52-mysql web/php-52/extension/php-mysql
>>
>> Why does "php-" have to be repeated
>>
>
> Um, the meaning is clear. Drop the second one and there's potential for
> confusion.
>
But they'd see "mysql" under php-52/extension.
> Especially if someone is looking for mysql in a non-php context ("oh, they've
> bundled
> it under php. Strange, but ... *shrug*).
>
>
>> 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
>
>
>> 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.
>
>
>> 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!
>
>
